dtsong

Use when designing component interaction specs with visual states, transitions, and accessibility requirements. Covers state matrices, responsive behavior, ARIA compliance, and content constraints. Do not use for multi-step user journey mapping (use journey-mapping).

Use when mapping complete user journeys through multi-step flows, onboarding sequences, or feature workflows. Covers entry points, happy paths, alternate paths, error states, friction analysis, and delight opportunities. Do not use for individual component interaction specs (use interaction-design).

Use when analyzing an existing codebase for architecture, tech stack, conventions, and infrastructure. Covers project structure mapping, data model discovery, integration point cataloging, and constraint identification. Do not use for schema changes (use schema-design) or API contract definition (use api-design).

Use when designing documentation architecture for a project or team. Covers audience mapping, Diataxis framework classification, onboarding path design, format and location decisions, documentation testing, and maintenance scheduling. Do not use for recording individual architecture decisions (use adr-template) or creating versioned changelogs (use changelog-design).

Use when auditing codebase patterns or evaluating proposed changes for convention consistency. Covers file naming, component patterns, data fetching, state management, and type conventions. Do not use for test plan design or coverage targets (use testing-strategy).

Use when classifying data elements by sensitivity tier and defining per-tier handling requirements. Covers data inventory, sensitivity classification, PII flow mapping, encryption and masking specifications, and cross-boundary transfer documentation. Do not use for regulatory gap analysis (use compliance-review) or audit logging design (use audit-trail-design).

Use when designing, evaluating, or versioning system prompts for LLM-powered features. Covers instruction structure, chain-of-thought patterns, output format constraints, few-shot example selection, and prompt versioning strategy. Do not use for RAG pipeline design (use rag-architecture) or AI evaluation frameworks (use ai-evaluation).

Use when designing features that exist in competing products or analyzing prior art in the market. Covers feature mapping, UX evaluation, technical trade-off assessment, and differentiation opportunity identification. Do not use for evaluating individual libraries (use library-evaluation) or assessing technology maturity (use technology-radar).

Fast codebase searches using grep/glob. Triggers on "find", "search", "where is", "grep for".

Use when working with dbt (data build tool) - creating models, writing tests, CI/CD pipelines, materializations, sources, staging/intermediate/marts layers, Snowflake/BigQuery warehouse configuration, incremental strategies, Jinja macros, data quality, semantic layer, or making analytics engineering decisions

Local git operations for syncing, branching, merging, and conflict resolution

GitHub interactions for issues, PRs, releases, and repository management

Interactive wizard to craft effective prompts using Claude Code best practices

Test-driven development reference for writing good tests, designing testable interfaces, mocking at system boundaries, and refactoring after green. Use when writing tests, reviewing test quality, or applying red-green-refactor workflow. Not for running test suites or CI configuration — use language-conventions or cicd-generation for those.

Use when working with Terraform or OpenTofu - creating modules, writing tests (native test framework, Terratest), setting up CI/CD pipelines, reviewing configurations, choosing between testing approaches, debugging state issues, implementing security scanning (trivy, checkov), or making infrastructure-as-code architecture decisions

Security audit checklist for web applications. Use when reviewing, auditing, or hardening a web app's security posture. Covers rate limiting, auth headers, IP blocking, CORS, security middleware, input validation, file upload limits, ORM usage, and password hashing. Triggers on requests like "review security", "harden this app", "security audit", "check for vulnerabilities", or when building/reviewing API endpoints.

Use when orchestrating monthly or quarterly close. Covers the close calendar, sub-ledger cutoffs, accruals, reclass entries, and post-close review. Do not use for individual reconciliations (use finance-reconciliation) or journal-entry construction (use finance-journal-entries).

Use when testing a SOX 404 control or designing a controls walkthrough. Covers control description, design effectiveness, operating effectiveness, deficiency evaluation, and remediation. Do not use for evidence-package preparation (use finance-evidence-package — Phase 3+).

Use when constructing a GAAP/IFRS journal entry from facts. Covers debit/credit selection, account coding, sub-ledger impact, and supporting memo. Do not use for reconciliation (use finance-reconciliation) or close orchestration (use finance-close-checklist).

Use when reconciling a balance-sheet account during the close cycle. Covers sub-ledger to GL ties, intercompany eliminations, exception triage, and audit-ready documentation. Do not use for journal-entry construction (use finance-journal-entries) or close orchestration (use finance-close-checklist).

Use when answering a federal, state, or international tax question that requires authoritative research. Covers IRC, Treasury Regs, Rev Rul/Proc, case law, and applicable treaty positions. Do not use for tax-provision computation (use finance-provision — Phase 3+).

Use when explaining actual-vs-plan or actual-vs-prior variance with commentary. Covers volume/price/mix decomposition, run-rate impact, and management commentary. Do not use for forecast revision (use finance-forecast-update — Phase 3+) or close orchestration (use finance-close-checklist).

Use when designing component interaction specs with visual states, transitions, and accessibility requirements. Covers state matrices, responsive behavior, ARIA compliance, and content constraints. Do not use for multi-step user journey mapping (use journey-mapping).

Use when mapping complete user journeys through multi-step flows, onboarding sequences, or feature workflows. Covers entry points, happy paths, alternate paths, error states, friction analysis, and delight opportunities. Do not use for individual component interaction specs (use interaction-design).

Security-first CI/CD workflow generation (GitHub Actions).

Build minimal, secure Dockerfiles with verification-first workflow.

Fast git snapshot for status, diff, and recent history.

Safe day-to-day git workflows for branching, sync, and cleanup.

Practical GitHub issue and pull request workflows using gh CLI.

Generate minimal-diff Helm values with schema-aware validation.

Project convention references for Python, TypeScript, and Terraform.

Terraform/OpenTofu authoring, testing, and security workflow.

Performs bank reconciliations between a bank statement export and GL cash detail. Use when the user provides a bank statement file (CSV, XLSX, or PDF) and a GL cash detail file and asks to reconcile, match transactions, identify outstanding items, or produce a bank rec workpaper. Outputs a matched/unmatched workbook, aged reconciling items, proposed adjusting JEs, and an evidence table.

Loads firm-specific accounting configuration including chart of accounts, materiality thresholds, close calendar, approval matrix, and standard mappings. Use at the start of any workflow that needs to apply firm-specific rules rather than generic accounting conventions.

Performs month-end flux/variance analysis against prior period and budget. Use when the user provides a trial balance and asks to analyze variances, explain fluxes, produce variance commentary, or build a flux workpaper. Applies firm materiality thresholds, calculates dollar and percent changes, categorizes variance type, drafts explanations where support exists, and generates targeted preparer questions where it doesn't.

Reviews proposed journal entries for posting readiness. Use when the user provides a list or file of journal entries and asks to review, validate, check for errors, or approve for posting. Verifies debit/credit balance, account coding, support adequacy, memo quality, period appropriateness, duplicate risk, and unusual patterns. Classifies each entry as ready, needs clarification, or reject.

Maps audit PBC request lists to support files, identifies gaps, drafts auditor responses, and assembles audit-ready evidence packages. Use when the user provides a PBC request list and a folder of support files and asks to match support to requests, identify missing items, flag duplicates or orphaned files, or draft responses to the auditor.

Builds and maintains prepaid expense amortization schedules. Use when the user provides vendor invoices, service period information, or an existing prepaid template and asks to extract prepaid items, build amortization schedules, calculate monthly expense, or generate journal entries for prepaid recognition and amortization. Produces a formula-driven schedule, not hardcoded tables.

Use whenever producing an accounting workpaper, schedule, reconciliation, journal entry, or audit deliverable. Defines firm formatting conventions, the evidence-table requirement, journal entry templates, and the standard for source tie-outs. Required dependency for bank-rec, flux-analysis, prepaid-schedule, pbc-package, and je-review skills.

Local git operations for syncing, branching, merging, and conflict resolution

GitHub interactions for issues, PRs, releases, and repository management

Use this skill when performing hardware security analysis for System-on-Chip components — threat modeling, verification scaffolding, compliance mapping, executive briefing, microarchitectural attack analysis, physical side-channel assessment, kernel security analysis, emerging hardware security, or TLA+ formal specification. Routes to the appropriate specialist. Trigger phrases include "threat model my SoC", "run STRIDE analysis", "generate SVA assertions", "compliance check against FIPS", "executive summary of findings", "Spectre analysis for cache", "DPA attack assessment", "kernel hardening review", "PQC hardware review", "TLA+ spec for access control". Do NOT use for software-only security, network security, or web application security.

Use when working with Terraform or OpenTofu - creating modules, writing tests (native test framework, Terratest), setting up CI/CD pipelines, reviewing configurations, choosing between testing approaches, debugging state issues, implementing security scanning (trivy, checkov), or making infrastructure-as-code architecture decisions

Security audit checklist for web applications. Use when reviewing, auditing, or hardening a web app's security posture. Covers rate limiting, auth headers, IP blocking, CORS, security middleware, input validation, file upload limits, ORM usage, and password hashing. Triggers on requests like "review security", "harden this app", "security audit", "check for vulnerabilities", or when building/reviewing API endpoints.

Use when a user asks to read, analyze, summarize, or extract from a heavyweight file (PDF, DOCX, PPTX, XLSX, CSV, TSV). Converts the file into markdown or CSV first, generates a lightweight index, and only spends model tokens on the compressed artifact. Trigger on "read this PDF", "look through this spreadsheet", "summarize this deck", or any time raw file ingestion would waste tokens. Do NOT trigger for plain text, markdown, JSON, YAML, or source code files — those are cheap to read directly.

TRIGGER_DESCRIPTION. Use when USER_CONTEXT. Routes to specialists for CAPABILITIES.

TRIGGER_DESCRIPTION. Use when USER_CONTEXT. Covers CAPABILITIES.