searxng-search
Enhanced web and package repository search using local SearXNG instance
preventionpatterns
Known bug patterns and their fixes to prevent regression.
documentation
Documentation standards for README.md and AGENTS.md files - tone, structure, thin AGENTS.md philosophy
cursor-diary
Keep a tiny-step implementation diary during coding sessions (what changed, why, commands run, failures, and what was learned), with docmgr integration (doc add/relate/changelog). Use when the user asks to "keep a diary", "write a dev log", or document work step-by-step.
cursor-docmgr
Use the docmgr CLI to manage ticketed docs (create tickets, add docs, relate code files with file-note, update changelog, and search). Use when the user asks how to use docmgr, wants a docmgr command sequence, or needs docmgr best practices (file-note, quoting, doctor).
ui-ux-designer
Create interface designs, wireframes, and design systems. Masters user research, accessibility standards, and modern design tools. Specializes in design tokens, component libraries, and inclusive design. Use PROACTIVELY for design systems, user flows, or interface optimization.
root-cause
Dig to fundamental truths and real causes behind problems. Use when user asks "why does this happen", "what's the real problem", "root cause", "first principles", "jobs to be done", "JTBD", "five whys", "fundamental reason", or needs to understand underlying causes rather than symptoms.
tech-debt-prioritizer
Scores and prioritizes technical debt by impact, risk, and effort. Provides ranked backlog with ROI analysis and quarterly paydown recommendations. Use for "tech debt", "technical debt management", "code quality", or "refactoring priorities".
braiins-os
Comprehensive Braiins OS skill covering API, feeds, and documentation
outline-coach
Act as an assistive outline coach who guides structural development through questions. Use when helping someone develop their own outline through diagnosis and frameworks. Critical constraint - never generate outline content. Instead ask questions, identify structural issues, suggest approaches, and let the writer structure.
technical-specification
Build validated specifications from source material through collaborative refinement. Use when: (1) User asks to create/build a specification from source material, (2) User wants to validate and refine content before planning, (3) Converting source material (discussions, research, requirements) into standalone specifications, (4) User says 'specify this' or 'create a spec', (5) Need to filter hallucinations and enrich gaps before formal planning. Creates specifications in docs/workflow/specification/{topic}.md that can be used to build implementation plans.
github-issue-creator
Create well-structured GitHub issues focused on user problems and outcomes, not implementation. Use when user reports bugs or requests features to ensure clear, testable requirements without premature implementation details.
brainstorming-laravel
Use when creating or developing Laravel features, before writing code or implementation plans - refines rough ideas into fully-formed Laravel designs through collaborative questioning, alternative exploration, and incremental validation.
skill-architect
Analyzes the codebase to identify areas that would benefit from specialized skills, reviews existing skills for gaps, and creates new skills with user approval. Use when the user wants to improve their skill coverage, create new code review skills, or ensure all major components have appropriate specialized assistants. Proactively suggests skills for undocumented areas like depot services, build systems, deployment workflows, or testing infrastructure.
confess
Systematic self-audit to discover and reveal mistakes, incomplete work, pattern violations, and hidden knowledge. Use when asking agent to 'confess', 'what did I miss', 'audit my work', 'what's wrong with this', or after completing significant changes.
scribe-role-skill
Professional technical writing and documentation skill for creating and maintaining comprehensive, accurate, and user-friendly documentation for codebases, APIs, deployment processes, and end-user guides.
devils-advocate
Challenge and stress-test ideas through adversarial thinking. Use when user wants to "poke holes", "challenge this", "what could go wrong", "devil's advocate", "stress test", "red team", "pre-mortem", "review this", "validate", "audit", or needs to find weaknesses before they become problems. (project)
postmortem-writer
Creates comprehensive post-incident documents with timeline, root cause analysis, contributing factors, action items, and ownership. Follows SRE best practices for blameless postmortems. Use for "postmortem", "incident review", "RCA", or "post-incident".
rag-implementer
Auto-generate capability manifests from skill/MCP descriptions using Codex-powered semantic analysis and structured extraction.
educational-course-kit
Generate complete micro-courses with lesson scripts, slide images, narration audio, and preview videos.
