voidful/Aixlarity

architecture-review

Use when evaluating whether a proposed change fits the existing architecture. Prevents layer violations, dependency cycles, and accidental coupling.

원문 언어: 영어

code-review

Use when the user wants a code review instead of implementation. Prioritizes correctness bugs, behavioral regressions, missing tests, and risky assumptions.

원문 언어: 영어

documentation-review

Use when reviewing documentation for accuracy, completeness, and alignment with source code. Catches doc-code drift before it confuses readers.

원문 언어: 영어

git-workflow

Use when making changes that should be committed. Enforces atomic commits, meaningful messages, and clean history.

원문 언어: 영어

performance-analysis

Use when investigating slow execution, high memory usage, or excessive token consumption. Systematic measurement before optimization.

원문 언어: 영어

refactoring

Use when improving code structure without changing behavior. Ensures each refactoring step preserves all existing tests.

원문 언어: 영어

security-audit

Use when reviewing code for security vulnerabilities. Covers prompt injection, path traversal, command injection, and agent-specific attack vectors.

원문 언어: 영어

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior. Four-phase root cause investigation. No fixes without understanding the problem first.

원문 언어: 영어

tdd

Use when implementing any feature or bugfix. Enforces RED-GREEN-REFACTOR cycle with test-first approach.

원문 언어: 영어

writing-plans

Use when you have a spec or requirements for a multi-step task. Creates implementation plans with bite-sized tasks, exact file paths, and verification steps.

원문 언어: 영어