Skill Creator

Cygnusfear

25 published skills · 0 GitHub stars across the catalog. View on GitHub ↗

4-step-program

Cygnusfear's avatarfrom 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.

architectural-analysis

Cygnusfear's avatarfrom 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.

audit

Cygnusfear's avatarfrom Cygnusfear

Run comprehensive codebase audit for gaps, deprecated code, TODOs, FIXMEs, architectural anti-patterns, type issues, and code smells. Use when user asks to audit code, find issues, check code quality, or identify architectural problems.

axiom-audit

Cygnusfear's avatarfrom Cygnusfear

Audit Axiom logs to identify and prioritize errors and warnings, research probable causes, and flag log smells. Use when user asks to check Axiom logs, analyze production errors, investigate log issues, or audit logging patterns.

blitz

Cygnusfear's avatarfrom Cygnusfear

This skill should be used when parallelizing multi-issue sprints using git worktrees and parallel Claude 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.

check-plan

Cygnusfear's avatarfrom Cygnusfear

Audit implementation progress against a plan, verify completed work, identify remaining tasks, and validate quality. Use when user asks to check plan status, verify implementation, see what's left to do, or validate plan completion.

chrome-devtools

Cygnusfear's avatarfrom 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.

comprehensive-code-review

Cygnusfear's avatarfrom Cygnusfear

This skill should be used when reviewing pull requests, performing comprehensive code review, analyzing code changes before merge, or when the user asks for thorough/ultra-critical code review. Performs EXTREMELY CRITICAL 6-pass analysis identifying runtime failures, code consistency issues, architectural problems, environment compatibility risks, and verification strategies. Posts structured review as GitHub PR comment. Use when user asks to "review PR", "review this code", "review changes", "check this PR", "analyze PR", "post review", or for Phase 3 of devflow. Supports parallel review mode with multiplier (code-review-3, code-review 6X) for consensus-based reviews. This is an ultra-critical reviewer that does not let things slip and desires only perfection.

create-mcp-skill

Cygnusfear's avatarfrom 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.

create-plan

Cygnusfear's avatarfrom Cygnusfear

Create comprehensive implementation plan in .plans directory based on analysis or report. Use when user asks to create a plan, plan implementation, design a solution, or structure work for a feature/refactor/fix.

create-pr

Cygnusfear's avatarfrom Cygnusfear

Create a PR for this branch. ALWAYS links related issues and uses closing keywords to auto-close them on merge.

create-skill

Cygnusfear's avatarfrom Cygnusfear

This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

create-subagent

Cygnusfear's avatarfrom Cygnusfear

This skill should be used when creating custom subagents for Claude Code, configuring specialized AI assistants, or when the user asks about agent creation, agent configuration, or delegating tasks to subagents. Covers both file-based agents and Task tool invocation.

delphi

Cygnusfear's avatarfrom 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 launches multiple oracle agents simultaneously with identical prompts, allowing them to independently explore and potentially discover different paths, clues, and solutions. Results are saved to .oracle/[topic]/ and synthesized into a final document.

design-spec-extraction

Cygnusfear's avatarfrom Cygnusfear

Extract comprehensive JSON design specifications from visual sources including Figma exports, UI mockups, screenshots, or live website captures. Produces W3C DTCG-compliant output with component trees, suitable for code generation, design documentation, and developer handoff.

devflow

Cygnusfear's avatarfrom Cygnusfear

End-to-end agent development process. Use when coordinating work, dispatching agents, or reviewing PRs.

file-name-wizard

Cygnusfear's avatarfrom Cygnusfear

Audit all filename and naming conventions in the codebase against CLAUDE.md standards and common patterns. Use when user asks to check naming conventions, audit filenames, find naming inconsistencies, or validate file naming patterns.

gh-ticket

Cygnusfear's avatarfrom Cygnusfear

Create or update comprehensive GitHub issues that capture ALL context, requirements, and implementation details. Use when creating or updating tickets, issues, feature requests, or bug reports. Ensures no context is lost between ticket creation and implementation - the moment you ask for a ticket, there's maximum context available that will be lost if not captured now.

obsidian-plan-wiki

Cygnusfear's avatarfrom Cygnusfear

This skill should be used when creating or working with modular project plans stored as Obsidian-compatible markdown wikis. Use when the user asks to create a plan, roadmap, or documentation system that needs to be navigable in Obsidian, or when working with existing plan wikis that use the %% [ ] %% task tracking format.

review-changes

Cygnusfear's avatarfrom 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.

superpower-zustand

Cygnusfear's avatarfrom 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

the-archivist

Cygnusfear's avatarfrom Cygnusfear

This skill should be used when engineering decisions are being made during code implementation. The Archivist enforces decision documentation as a standard practice, ensuring every engineering choice includes rationale and integrates with Architecture Decision Records (ADRs). Use when writing code that involves choosing between alternatives, selecting technologies, designing architectures, or making trade-offs.

the-oracle

Cygnusfear's avatarfrom 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.

update-docs

Cygnusfear's avatarfrom Cygnusfear

Update all documentation in .plans, CLAUDE.md files, docs, and .tasks to match current codebase state. Use when user asks to update docs, refresh documentation, sync docs with code, or validate documentation accuracy.