Loading...
Loading...
Found 435 Skills
Phase 2 of the feature workflow —— Write code according to the implementation sequence in {slug}-design.md, and submit a completion report in a unified format for user review after finishing. Prerequisites: {slug}-design.md has been approved (standard design includes test design, or fastforward design includes acceptance criteria), and {slug}-checklist.yaml exists in the same directory. Trigger scenarios: User says "The plan is confirmed, start implementation", "Write code according to the plan", "Start working". If you encounter situations not covered by the plan during implementation (new concepts, out-of-scope files, need for patch branches), proactively stop and go back to discuss the plan instead of pushing forward blindly.
Ultra-lightweight channel for refactor processes - used when changes are clearly too small to go through the full scan → design → apply three-stage workflow. AI directly identifies 1-3 low-risk optimization points, confirms with the user once, modifies in-place using classic methods, and validates itself by running tests. No scan checklist, no design documentation, no multi-step human verification required. Trigger scenarios: User says "quick refactor", "small refactor", "simply optimize XX function", "modify directly", "skip the extra steps", and the scope of changes is clearly localized to a single function / single component with test coverage for self-validation.
Design for everyone by treating accessibility as a first-class design discipline, not a compliance checklist. Part of the Intent design strategy system. Covers WCAG 2.2 for designers, screen reader experience design, keyboard navigation, cognitive accessibility, motor accessibility, inclusive design beyond compliance, and accessibility testing methodology. Trigger on: accessibility, a11y, WCAG, screen reader, keyboard navigation, color contrast, alt text, focus management, touch targets, inclusive design, assistive technology, "is this accessible", "check accessibility", "design for everyone", "who are we excluding", ADA compliance, Section 508, EAA, reduced motion, or any question about whether all users can perceive, operate, understand, and benefit from the experience. One billion people worldwide have a disability. Everyone experiences situational impairment. Designing inclusively makes the experience better for everyone.
Pre-production audit that scans a codebase for security, database, deployment, code quality, AI/LLM, dependency, frontend, and observability issues. Intercepts deploy commands and blocks until critical items pass. Stack-agnostic. Use for "run ship gate", "am I ready to ship", "pre-launch audit", "can I deploy", "push to production", "go live checklist", "preflight check". Not for CI/CD setup or infra provisioning.
Suggest tests worth writing for a feature using the ZOMBIES heuristic (Zero, One, Many, Boundaries, Interface, Exceptions, Simple scenarios). Pass a free-text feature description, or omit args to use the current branch's diff. Outputs only the categories that apply — not a full ZOMBIES checklist.
Guides people operations (HR ops)—employee lifecycle administration, HRIS workflows, onboarding and offboarding checklists, handbook and policy rollout, benefits and payroll coordination, performance review cycles, leave and PTO process, and people data hygiene. Use when running new-hire onboarding, offboarding, HR policy communications, performance cycle logistics, org change updates in HRIS, or employee-facing process design—not for corporate board governance (corporate-counsel), commercial contract redlines (commercial-counsel), SOC audit evidence (compliance-engineer), or customer success onboarding (customer-ops-specialist). Escalate employment law questions to qualified counsel.
Set up a Markdown-based local ticket management system for your project. Create task, bug, and chapter tickets in the .local/ticket/ directory, and track progress using checklists. It can be used casually since it is not managed by Git. Language and framework agnostic. Use when requested: "introduce ticket system", "task management with Markdown", "set up local ticket management", "create ticket", "create bug ticket", "create chapter", "create epic", "local ticket system", "setup ticket management".
Performs a comprehensive security review of code changes in a GitHub PR or issue. Checks out the branch, analyzes changed files against a 9-category security checklist, and produces PASS/WARNING/FAIL verdicts. Use when reviewing pull requests for security vulnerabilities, hardcoded secrets, injection flaws, auth bypasses, or insecure configurations. Trigger keywords - security review, code review, appsec, vulnerability assessment, security audit, review PR security.
Guardião da qualidade de código e entregas no SynkOS. Use esta skill quando o usuário pedir para revisar código implementado, executar gates de qualidade, fazer code review, validar se uma story atende os critérios de aceite, checar segurança (OWASP), ou fazer perguntas como "revise o código da story X", "o que passou no gate de qualidade?", "há problemas de segurança?", "a implementação cobre os critérios de aceite?", "rode o code review automatizado". Ative também para documentar findings com severidade, decidir PASS/CONCERNS/FAIL/WAIVED para stories, e devolver ao dev com checklist de correções quando a story falha.
Detect AI-generated code patterns ("slop") in PHP/Laravel and TypeScript/React source — comment narration, generic naming, premature interfaces, defensive overdose, mock-everything tests, and the absence of human "scars". Use when reviewing AI-assisted PRs, auditing code for taste/quality (not metrics — that's technical-debt), or hardening a code-review checklist. Triggers on "review for AI slop", "find AI patterns", "check code feels human", "audit code-quality taste".
Standalone quality review for Elastic integrations. Classifies files by domain, loads domain-specific skills and review checklists, applies cross-domain consistency rules, CEL version verification, API conformance, and severity calibration. Input-agnostic: works on local packages, PR diffs, or branch comparisons. Use when reviewing integration quality independently of any build or fix workflow.
Comprehensive code review skill for TypeScript, JavaScript, Python, Swift, Kotlin, Go. Includes automated code analysis, best practice checking, security scanning, and review checklist generation. Use when reviewing pull requests, providing code feedback, identifying issues, or ensuring code quality standards.