Cygnusfear
@Cygnusfear
Public Skills
create-mcp-skill
by Cygnusfear
Create a new skill that uses an MCP server, following best practices from the MCP CLI guide. Use when user wants to create a skill for a new MCP server or integrate MCP functionality into a skill.
4-step-program
by Cygnusfear
Coordinator workflow for orchestrating dockeragents through fix-review-iterate-present loop. Use when delegating any task that produces code changes. Ensures agents achieve 10/10 quality before presenting to human.
design-spec-extraction
by Cygnusfear
Use when extracting design specifications from visual sources including Figma exports, UI mockups, screenshots, or live website captures. Produces W3C DTCG-compliant JSON with component trees for code generation and developer handoff.
writing-clearly-and-concisely
by Cygnusfear
Use when writing any prose humans will read — documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules to make writing clearer, stronger, and more professional.
superpower-zustand
by Cygnusfear
MANDATORY for creating Zustand stores. This skill is required when users request state management, creating stores, or mention Zustand. Do NOT create Zustand stores without this skill - all stores must use the required StoreBuilder pattern with immer middleware and factory pattern separation
create-skill
by Cygnusfear
This skill should be used when users want to create a new skill (or update an existing skill) that extends your capabilities with specialized knowledge, workflows, or tool integrations.
the-oracle
by Cygnusfear
This skill should be used when the user asks to "use the oracle" or "ask the oracle" for deep research, analysis, or architectural questions. The oracle excels at multi-source research combining codebase exploration and web searches, then synthesizing findings into actionable answers. Use for complex questions requiring investigation across multiple sources, architectural analysis, refactoring plans, debugging mysteries, and code reviews.
create-pr
by Cygnusfear
Create a PR for this branch. ALWAYS links related issues and uses closing keywords to auto-close them on merge.
create-worker
by Cygnusfear
This skill should be used when creating custom agents for Claude Code, configuring specialized AI assistants, or when the user asks about agent creation, agent configuration, or delegating tasks to workers. Covers both file-based agents and teams delegation.
ticket
by Cygnusfear
Use when a skill needs to persist output as a standardized artifact — research findings, plans, postmortems, reviews, design specs, decisions. Replaces bespoke output directories with a single canonical tk ticket system.
using-superpowers
by Cygnusfear
Guidelines for using skills effectively - load relevant skills before complex tasks, not every message
chrome-devtools
by Cygnusfear
Control Chrome browser programmatically using chrome-devtools-mcp. Use when user asks to automate Chrome, debug web pages, take screenshots, evaluate JavaScript, inspect network requests, or interact with browser DevTools. Also use when asked about browser automation, web scraping, or testing websites.
brainstorming
by Cygnusfear
"You MUST use this, UNLESS the human says otherwise, before any EXTENDED creative work (not simple execution) - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation."
delphi
by Cygnusfear
This skill should be used when the user asks to "use delphi", "ask delphi", or wants multiple parallel oracle investigations of the same question to discover divergent insights. Delphi delegates to multiple oracle workers simultaneously with identical prompts, allowing them to independently explore and potentially discover different paths, clues, and solutions. Results are saved as tickets tagged research,delphi and synthesized into an epic ticket.
obsidian-plan-wiki
by Cygnusfear
Create and manage behavior specification wikis in Obsidian format. Use when creating specs, documenting features, or when user mentions "wiki", "spec", "feature", or "Obsidian".
video-explorer
by Cygnusfear
This skill should be used when analyzing video files. You cannot process video directly, so this skill extracts frames hierarchically - starting with a quick overview, then zooming into regions of interest with higher resolution and temporal density. Use when asked to watch, analyze, review, or understand video content.
blitz
by Cygnusfear
This skill should be used when parallelizing multi-issue sprints using git worktrees and parallel agents. Use when tackling multiple GitHub issues simultaneously, when the user mentions "blitz", "parallel sprint", "worktree workflow", or when handling 3+ independent issues that could be worked on concurrently. Orchestrates the full workflow from issue triage through parallel agent delegation to sequential merge.
update-docs
by Cygnusfear
Update all documentation in docs and AGENTS.md files to match current codebase state. Use when user asks to update docs, refresh documentation, sync docs with code, or validate documentation accuracy.
writing-plans
by Cygnusfear
Use when you have a spec or requirements for a multi-step task, before touching code
writing-skills
by Cygnusfear
Use when creating new skills, editing existing skills, or verifying skills work before deployment
domain-first-architecture-delphi
by Cygnusfear
Use when architecture feels component-based but ownership is split across technical buckets (tables/init/debug), causing god files, duplicate paths, and hidden dependency flow.
file-name-wizard
by Cygnusfear
Audit all filename and naming conventions in the codebase against AGENTS.md standards and common patterns. Use when user asks to check naming conventions, audit filenames, find naming inconsistencies, or validate file naming patterns.
review-changes
by Cygnusfear
Code review of current git changes, compare to related plan if exists, identify bad engineering, over-engineering, or suboptimal solutions. Use when user asks to review changes, check git diff, validate implementation quality, or assess code changes.
architectural-analysis
by Cygnusfear
Deep architectural audit focused on finding dead code, duplicated functionality, architectural anti-patterns, type confusion, and code smells. Use when user asks for architectural analysis, find dead code, identify duplication, or assess codebase health.