Cygnusfear
- 20 skills
- 0 followers
- 10 hours ago last updated
- ▌ Environment · cygnusfearWorking in the pi-extensions environment — code-mode, persistence, memory, search, delegation, and context management. Read this first.
- ▌
- ▌ Frontpage · cygnusfearUse when chat output is getting dense — tables, comparisons, architecture, graphs, evolving findings. Compose an HTML frontpage via `frontpage_create` instead of typing raw HTML. Structured spec in, editorial page out. Mermaid / Chart.js / D3 / bespoke HTML all supported.
- ▌ Mai Pr · cygnusfearUse when creating, reviewing, or merging pull requests through mai. Git-native PRs stored as notes — no GitHub, no Forgejo, no platform lock-in. Covers creation, review (accept/reject), submission (merge), auto-close, and diff inspection.
- ▌ Mai Adr · cygnusfearUse when recording architecture decisions (ADRs). Decisions are kind:decision notes attached to code via --target, queryable via mai ls/context, and optionally materialize as markdown files. Covers detection triggers, tier system, comment templates, and anti-patterns.
- ▌ Mai Agent · cygnusfearUse when working in any git repo with maitake. Check for notes before touching files, leave notes after meaningful work. This is the base agent contract — all other mai skills build on it.
- ▌ Mai Setup · cygnusfearUse when setting up maitake in a repo for the first time, configuring sync to a remote, or troubleshooting the setup.
- ▌ Mai Review · cygnusfearUse when performing code review or requesting changes. Leave findings directly on files with acceptance criteria and rejection criteria. Fix agents see findings in-place via mai context.
- ▌ Mai Harness · cygnusfear bundleUse when a repo needs durable mai-backed context so every agent sees rules, rationale, and hazards before editing code. Covers promoting chat knowledge into tickets, constraints, warnings, ADRs, artifacts, and reviews; mirroring critical items into AGENTS.md; and enforcing mai context usage through arrival rituals, delegation templates, review gates, and verification.
- ▌ Mai Research · cygnusfearUse when conducting research, oracle investigations, or delphi consultations. Save findings as mai notes with proper tags and structure.
- ▌ Mai Constraint · cygnusfearUse when setting or checking project rules that all agents must follow. Constraints show up in mai context alongside tickets and warnings. They stay open until the rule changes.
- ▌ Mai Orchestrate · cygnusfearUse when coordinating work across multiple agents via teams. Create tickets, delegate, track deps, monitor progress, run reviews — all through mai.
- ▌ Delphi · cygnusfearThis 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.
- ▌ Create Pr · cygnusfear bundleCreate a PR for this branch. ALWAYS links related issues and uses closing keywords to auto-close them on merge.
- ▌ Axiom Audit · cygnusfearONLY USE WHEN REPO IS USING AXIOM LOGGING. 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.
- ▌ Comprehensive Code Review · cygnusfearThis 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.
- ▌ Brainstorming · cygnusfearYou 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.
- ▌ Using Superpowers · cygnusfearGuidelines for using skills effectively - load relevant skills before complex tasks, not every message
- ▌ Obsidian Plan Wiki · cygnusfear bundleCreate and manage behavior specification wikis in Obsidian format. Use when creating specs, documenting features, or when user mentions "wiki", "spec", "feature", or "Obsidian".
- ▌ Writing Clearly And Concisely · cygnusfear bundleApply Strunk's timeless writing rules to ANY prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Makes your writing clearer, stronger, and more professional.