Loading...
Loading...
Found 446 Skills
Claude Code settings file hierarchy, permission wildcards, and configuration patterns. Use when setting up project permissions, debugging settings issues, or understanding why certain tools are allowed or blocked.
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
Comprehensive context management strategies for cost optimization and infinite-length conversations. Covers server-side clearing (tool results, thinking blocks), client-side SDK compaction (automatic summarization), and memory tool integration. Use when managing long conversations, optimizing token costs, preventing context overflow, or enabling continuous agentic workflows.
Inline adversarial plan review — 3 sequential checks (Feasibility, Completeness, Scope & Alignment) performed by the calling LLM in its own context. No subagents spawned. Call after saving a plan. Returns GATE_PASS or GATE_FAIL with blocking issues.
Open a new context session at the start of a leader agent workflow. Records agentName, storyId, and phase in wint.contextSessions, emitting a structured SESSION CREATED block for downstream workers to inherit.
Enforce low Cognitive Complexity (SonarSource) and low Cyclomatic Complexity in ALL code written or modified, in any programming language, framework, or platform. This skill MUST activate automatically whenever code is being written, generated, modified, or refactored — no explicit trigger needed. Triggers include writing any function, method, class, module, script, handler, endpoint, test, or code block. Also triggers on "low complexity", "cognitive complexity", "cyclomatic complexity", "reduce complexity", "simplify code", "too complex", "refactor for readability", "clean code", "implement", "fix bug", "add feature", "generate test", "optimize", "rewrite", "scaffold".
Deterministic tmuxx CLI + interactive TUI with pane-level activity insights. Use for tmux orchestration, worktree task execution, and real-time visibility into which agents are running, idle, or blocked on user input. CLI with JSON output for agents; TUI with visual status indicators for humans.
Expert at evaluating software projects for production readiness. Assesses codebases holistically to determine what's shippable, what's blocking launch, and how to get from current state to "good enough to charge money for."
Creates and organizes focused planning views from a subset of roadmap tasks. Use when the user wants to build a task graph, analyze dependencies, identify ready or blocked work, or group near-term and future work into a focused planning workspace.
Creates and refines Founder Story and brand narrative content for DTC/independent stores selling founder-driven products (e.g. handcrafted leather, artisan sauces, small-batch goods). Use whenever the user mentions founder story, brand story, about page, origin story, artisan brand, handcrafted brand, "who we are" copy, brand voice, mission/vision for a product brand, landing page hero narrative, PDP brand block, or wants to differentiate through authenticity and founder-led storytelling—even if they do not say "founder story" explicitly. Output structured narrative frameworks, placement guidance, and ready-to-use copy aligned with DTC best practices.
Audit Airtable bases for migration readiness — runs analysis, reads the report, and delivers a structured verdict with complexity verdict, blockers, schema recommendations, and concrete next steps. Use when the user wants to "analyze my Airtable", "migrate from Airtable", "audit Airtable data quality", "export Airtable to PostgreSQL", or "understand my Airtable schema".
Show the current health status of a GRACE project. Use to get an overview of project artifacts, codebase metrics, knowledge graph health, and suggested next actions — helps identify drift, missing contracts, or unpaired semantic blocks.