All authors
Claude Skills by JustineDevs
github.com/JustineDevs11 skills0 installs24 views
- AlignUse when the user needs scope alignment, shared language, or docs clarity before or between gated lanes.Votes: 0GitHub stars: 5
- ArchUse when the user wants architecture-first product and system design with explicit stack rationale, boundaries, tradeoffs, data model choices, and phased delivery planning.Votes: 0GitHub stars: 5
- BuildUse when the user wants to decide whether implementation is ready, what remains blocked, and what the exact next build step should be.Votes: 0GitHub stars: 5
- CleanupUse when the user wants contract-preserving simplification, anti-slop cleanup, or a final-pass polish after the main decision is made.Votes: 0GitHub stars: 5
- DiagnoseUse when the user needs failure triage, blocked-lane diagnosis, or root-cause decomposition before the next gate can move.Votes: 0GitHub stars: 5
- FlowUse when the user wants logic validation: states, transitions, invariants, edge cases, dead ends, and blockers before implementation.Votes: 0GitHub stars: 5
- MaestroUse when the user wants the singular Meta-Architect in-session autonomous manager: choose the best next workflow step, manage the fixed gated workflow, and route bounded helper handoffs inside Codex.Votes: 0GitHub stars: 5
- SageUse when the user wants evidence-backed technology choices, OSS evaluation, and source-grounded validation of the stack proposed in `$arch`.Votes: 0GitHub stars: 5
- TddUse when the user wants regression-first or test-first scaffolding before implementation work expands.Votes: 0GitHub stars: 5
- VetUse when the user wants a security and trust-boundary review of the current design before implementation or release.Votes: 0GitHub stars: 5
- VibeUse when the user wants a DX and UX review of the planned workflow before implementation proceeds.Votes: 0GitHub stars: 5