Use when requirements, KPI definitions, permissions, financial treatment, statuses, date semantics, exception handling, or acceptance…
Guides reliable software deployment for environments lacking automated CI/CD pipelines using a robust script-based framework.
Framework-less PHP knowledge base. Provides pure PHP project architecture, DDD integration, PSR-7/PSR-15 HTTP, standalone persistence, DI…
Use when reporting findings, progress, or asking for approval to someone who owns the product but does not read the code, when the reader…
Use when product or application logic may contain contradictory states, mixed date or filter scopes, KPI/card mismatches, misleading…
Validate your code changes through the no-mistakes pipeline - automated code review, tests, lint, docs, push, PR, and CI - before they…
This skill should be used when the user is configuring SSO, setting up CI/CD authentication, designing OIDC federation, eliminating SSH…
Use when reviewing a product artifact or implementation handoff that contains proposed or implied screens, navigation, roles, workflows…
Use when reporting task status, completion, blockers, percentages, ETAs, test results, deployment readiness, or handoff progress where…
Use when fixing bugs, refactoring, changing shared state, or reviewing a patch where behavior that already works could regress; triggers…
Use when planning, implementing, debugging, or reviewing work where the solution could expand beyond the user's requested outcome…
Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in.
Spawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it.
Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform.
Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after…
Use for \"how does X work\", code walkthroughs before changing something, and placement / ownership / layering questions (\"where should…
Index of the engineering principles. Load it whenever work is non-trivial: designing types or a signature, refactoring, debugging…
Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes…
Keep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result).
Fan out N parallel workers, drain them, and return one report.
Select only required columns to reduce memory and transfer costs; apply to base queries and relations