scwa-framework

Design and scaffold APIs with contracts, validation, error handling, tests, documentation, and consumer impact awareness.

Diagnose bugs systematically by reproducing, isolating, explaining root cause, implementing the smallest safe fix, and adding regression protection.

Create or update project documentation, setup guides, architecture notes, CLAUDE.md, runbooks, and developer-facing references.

Find and fix performance bottlenecks across frontend, backend, database, and test suites using evidence-first analysis.

Improve structure, readability, modularity, and maintainability without changing behavior, while preserving safety with tests.

Perform senior-level code review for correctness, edge cases, security, performance, typing, maintainability, architecture fit, and missing tests.

Audit code and workflows for practical security issues including auth flaws, injection risk, insecure defaults, data exposure, and secrets handling.

Create focused, reusable Claude Code skills from repeated workflows, review patterns, debugging playbooks, and team conventions.

Generate or improve tests with strong coverage of behavior, edge cases, negative paths, and regression protection.

Test web applications using Playwright with stable locators, deterministic assertions, trace-first debugging, and defect-oriented reporting.

8-layer structured code review. Use before any PR, merge, or deploy. Triggers on "review this code", "review my PR", "check this before I merge", "ai review", or when the user shares a diff, file, or code block requesting evaluation. Covers logic, edge cases, security, payroll compliance, error handling, performance, test coverage, and readability — in that order by severity.

Formal defect lifecycle — triage, isolation, fix, verification, and closure report. Use when a defect has been reported via QA, production incident, or bug ticket. Triggers on "defect", "bug report", "production issue", "ticket", "incident", or any request referencing a specific defect ID, customer report, or QA-found issue. Distinct from systematic-debug which covers ad-hoc investigation.

Full-stack feature builder — schema to API to UI with explicit contract validation at each layer. Use when building features that span database, backend, and frontend. Triggers on "build a feature", "add X to the app", "create an endpoint and UI for", "full stack implementation", or any request requiring changes across 3 or more layers simultaneously.

Always-active behavioral guardrail. Enforces four rules on every coding interaction — no silent assumptions, minimal solutions, orthogonal change prevention, and verification before execution. This skill is ALWAYS active. Not domain-specific. Applies to every session, every prompt, every tool call.

6-layer pre-code architecture mapping skill. Use before writing any non-trivial implementation to map the full architectural surface before the first line of code. Triggers on "architect this", "map the architecture", "design before build", or automatically when spec-architect Phase 2 involves cross-system impact. Outputs a layered architecture map that feeds into DECISIONS.md.

Pre-code specification protocol. Use before implementing any feature, module, or service that touches business logic, data models, or external integrations. Triggers on "implement", "build", "create feature", "add endpoint", "design schema", or any request where code is the expected output but requirements are unstated. Does NOT trigger for quick fixes under 10 lines, config changes, or documentation.

5-phase structured debugging protocol. Use when encountering any bug, test failure, unexpected behavior, production incident, or error trace. Triggers on "debug this", "why is this failing", "fix this error", "this isn't working", stack traces, error messages, or failed test output anywhere in the prompt. Always runs before proposing any fix.

Test-Driven Development enforcement. Use when implementing new features, fixing bugs, or adding business logic. Triggers on "write tests", "implement with TDD", "add tests then code", or any implementation request for business logic where the user has not provided pre-existing failing tests. Also activates automatically before Phase 4 of the spec-architect skill.