Claude Skills by tranhieutt

Orchestrates the backend team of technical-director, backend-developer, data-engineer, and security-engineer to design, implement, and review a backend system end-to-end. Use when a backend feature needs coordinated multi-specialist delivery.

Orchestrates a cross-functional feature team of product-manager, ux-designer, frontend-developer, backend-developer, and qa-engineer to deliver a complete feature from specification to tested implementation. Use when a feature requires full-stack coordinated delivery.

Orchestrates the frontend team of ux-designer, ux-researcher, frontend-developer, and accessibility-specialist to design, implement, and validate a UI feature from research to launch. Use when a UI feature needs coordinated design and engineering delivery.

Orchestrates the release team of release-manager, qa-engineer, devops-engineer, and producer to execute a release from candidate to production deployment. Use when coordinating a release across QA, DevOps, and release management.

Orchestrates the UI team of ux-designer and ui-programmer to design, implement, and polish a UI feature from wireframe to final implementation. Use when a UI component or page needs both design and engineering coordination.

Scans the codebase for technical debt indicators, categorizes and prioritizes findings, and maintains a debt register with repayment recommendations. Use when assessing codebase health, planning refactoring, or when the user mentions technical debt or code quality.

Forces the strict Red-Green-Refactor development cycle. Requires one failing behavior test through a public interface before each implementation slice.

Reads and filters production/traces/decision_ledger.jsonl to display a timeline of agent decisions. Supports filtering by agent, risk_tier, task_id, outcome, and date range.

Guidelines and procedures for creating comprehensive UI Specifications from PRDs and prototypes.

Unlocks the codebase after a release freeze or incident freeze period to resume normal development. Use when a freeze period ends or when the user mentions unfreezing or lifting the code freeze.

Updates docs/technical/CODEMAP.md by scanning the current codebase structure. Run after a significant feature merge, refactor, or when CODEMAP feels stale.

Routes every software-development request through the right SDD workflow before action. Use at session start, before clarifying questions, before edits, and whenever deciding which SDD skill should govern a task.

Provides vector database and semantic search patterns for Pinecone, Weaviate, Qdrant, Milvus, and pgvector in RAG and recommendation systems. Use when implementing vector search or when the user mentions vector database, semantic search, embeddings, or similarity search.

Requires fresh verification evidence before claiming work is complete, fixed, passing, safe, ready, merged, or clean. Use before completion claims, commits, PRs, merge readiness, or moving to the next task.

Guidelines and procedures for planning and implementing end-to-end functional slices for fullstack features.

Generates high-fidelity architecture diagrams, sequence flows, and component maps for SDD projects. Use when finalizing a design phase, documenting system architecture, or visualizing agentic workflows. Default style: Style 6 (Claude Official).