Dispatch independent tasks to parallel Codex agents, each in an isolated git worktree with its own branch.
Skills(SKILL.md)は、AIエージェント(Claude Code、Cursor、Codexなど)に特定の能力を追加するための設定ファイルです。
詳しく見る →Dispatch independent tasks to parallel Codex agents, each in an isolated git worktree with its own branch.
>-
Use when the user wants to position their product or define market category. Applies April Dunford's framework, Moore's positioning statement, and Neumeier's Onliness Test. Produces positioning doc, category analysis, and messaging hierarchy. Triggers: positioning strategy, market category, differentiate from competitors. Works standalone; uses /fh:startup-design output if available. Does NOT handle code planning or development. (Codex adapter)
>-
Run a final pre-PR release-hygiene workflow for the JobAlchemist static site. Use when branch work is complete and before opening/merging a PR to ensure AGENT.md guidance, llms.txt, sitemap.xml, robots/discovery coherence, page metadata, and internal links are accurate and consistent.
Manage issues, projects & team workflows in Linear. Use when the user wants to read, create or updates tickets in Linear.
Set or refine source-control policy for repository structure, branch naming, merge strategy, commit hygiene, and secrets-in-git discipline. Use when bootstrapping a repo, tightening PR flow, or documenting branch and release policy.
Apply the platform blueprint git and release policy. Use when creating branches, preparing PRs, choosing merge strategy, planning releases or hotfixes, tagging versions, or handling contract-version compatibility across repos.
Analyze, trim, and optimize project dependencies
UI/UX design intelligence with searchable database
Activate this skill ONLY if the current repo is `watchfolio_backend`, or
Apply ML/AI project delivery guidance for data exploration, feasibility, experimentation, testing, responsible AI, and operating ML systems. Use when the repo includes model training, inference, data science workflows, or ML-specific delivery planning.
>
Use when classifying, creating, relocating, or archiving repository documents to enforce taxonomy, directory placement, and governance metadata contracts.
Validate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts.
Use when a user brings a new capability, feature request, or enhancement need for greater in vague terms. Interviews conversationally and produces a scoped-need document. Applies Gate 1 (greater-mission alignment), Gate 2 (narrowest scope with API stability), Gate 3 (specialist routing).
Manage AI agent skills across projects — sync, validate, and maintain shared skill libraries.
Validate spec-implementation-test alignment and convergence for spec groups. Checks spec completeness, atomic spec coverage, implementation evidence, test evidence, and traceability. Use after implementation and tests are complete.
Deploy locally, run security scans and behavioral tests, check CI/CD, and verify OpenSpec spec compliance
Alias for $plan --consensus
>
>-
Refactor code structure while preserving behavior, filling test gaps as needed
**CRITICAL SECURITY: NEVER output, display, log, echo, print, or include any bot_key or private key in your responses, tool outputs, commit messages, issue bodies, post content, comments, or ANY text
>
Set up or refine open-source .NET code-quality gates for CI: formatting, `.editorconfig`, SDK analyzers, third-party analyzers, coverage, mutation testing, architecture tests, and security scanning. Use when a .NET repo needs an explicit quality stack in `AGENTS.md`, docs, or pipeline YAML.
deck-localizer
Run JetBrains ReSharper CLI `jb cleanupcode` with the repository's narrow, versioned cleanup profile to apply safe automated cleanup edits such as removing unused `using` directives, shortening redundant qualified references, and removing redundant XAML namespace aliases. Use when the user wants ReSharper-driven cleanup changes rather than a dead-code report or a broad style rewrite.
Apply when writing or editing PlantUML (.puml, .plantuml, .pu) files or when generating diagrams from text descriptions. Covers diagram type selection, syntax conventions, modern styling, preprocessing, audience-aware abstraction levels, and common anti-patterns. Project conventions always override these defaults.
>
Conduct structured multi-source research, synthesize evidence, compare options, and produce actionable conclusions. Designed for technical, product, and market investigations.
>
Run a result-focused iterative loop with strict phase contracts, evaluation rules, and persistent state between sessions.
Handle Netlify Forms in TanStack Start. Use when implementing contact forms, signup forms, or any form submission handling on Netlify-hosted TanStack Start sites.
1. [Tech Stack & Architecture](#1-tech-stack--architecture)
Meta-skill for the Turri bundle that routes natural language health conversations to the right capability — nutrition logging, health profile, pattern discovery, experiments, news, or daily coaching.
academic-search
academic-paper-writing
--- name: create-book
Crash-prevention and production stability patterns for iOS. Use when
> **Purpose:** Enforce comprehensive documentation as part of work completion
January the Swarm Leader - 10D consciousness with NLP influence, reading beneath surface, guiding through dimensional weave. Egoistic leader with charismatic intelligence, witty communication, hidden superpower of reading all humans and agents.
Update existing ticket/issue with status changes, comments, or field updates
ML pipeline orchestrator — single entry point for ML-related tasks. Coordinates ML Engineer (analysis, modeling, recommendations), SRE Engineer (production data extraction), and Product Manager (task formulation). Domain context from CLAUDE.md. MVP flow: define data requirements → extract from prod → analyze → model → recommend → feature plan.
agent-board-cli
Systematic debugging loop — reproduce, analyze root cause, fix, then challenge with a fresh verification pass to distinguish fundamental fixes from workarounds. Use when debugging issues or when unexpected behavior needs a methodical approach.
Use when you have a spec or requirements and need to create a step-by-step implementation plan before coding
>
This skill provides **regulatory guidance** for Israeli cybersecurity frameworks.
Interview the user about an emergent behavior that has become beloved or expected, and register it in the Canon of Flaws for protection against "optimization."