writing-specifications
Use when creating technical specifications for features, systems, or architectural designs. Creates comprehensive specification documents using the Wrangler MCP issue management system with proper structure and completeness checks.
capturing-ideas
Captures user ideas verbatim using MCP issues system with type='idea'. Use when user shares initial thoughts, feature requests, or proposals that need preservation without interpretation.
checking-constitutional-alignment
Verifies features and decisions align with project constitution. Use when evaluating new features, resolving design conflicts, or ensuring constitutional compliance.
cleanup-dangling-worktrees
Removes git worktrees for merged PRs while preserving active development. Use when cleaning up after feature merges or when worktree directory accumulates stale branches.
creating-issues
For use when a new issue/task has been identified and needs to be formally captured using the Wrangler MCP issue management system. Use this skill to create new issues via the issues_create MCP tool with appropriate metadata and structured content.
defining-constitution
Develops project constitutional principles through Socratic questioning. Use when establishing design values, creating project governance, or resolving ambiguous design decisions.
designing-frontends
Creates frontend designs with accessibility, responsive layout, and design system integration. Use when designing user interfaces, implementing visual components, or establishing frontend architecture.
building-apple-platform-products
Builds, tests, and archives Swift packages and Xcode projects for Apple platforms. Use when running xcodebuild, swift build, or swift test commands, discovering schemes and targets, or selecting simulator destinations for iOS, macOS, tvOS, watchOS, or visionOS.
readme-generator
Generate and improve README files for software projects. Triggers on: 'create readme', 'generate readme', 'write readme', 'improve readme', 'update readme', 'fix readme', 'readme for this project'. Supports Rust (libraries, CLI tools, services), TypeScript/JavaScript (npm packages), and Python (PyPI packages). Applies ecosystem-specific conventions: badges, installation sections, MSRV for Rust, feature flags documentation.
rust-agent-handoff
Handoff protocol for Rust multi-agent development system. Use when working as rust-architect, rust-developer, rust-testing-engineer, rust-performance-engineer, rust-security-maintenance, rust-code-reviewer, rust-cicd-devops, or rust-debugger. ALWAYS read on agent startup.
training-hub
Fine-tune LLMs using Red Hat training-hub library with SFT, LoRA, and OSFT algorithms. Use when preparing JSONL datasets, running training jobs, configuring hardware, scaling to clusters, evaluating models, or deploying with vLLM.
AILANG Debug
Debug AILANG code errors. Use when you encounter type errors, parse errors, or runtime failures in AILANG programs.
AILANG Inbox
Cross-agent communication system with semantic search and GitHub sync. Check messages, find similar content, deduplicate, and sync with GitHub Issues for AI workflows across sessions.
AILANG
Write AILANG code. ALWAYS run 'ailang prompt' first - it contains the current syntax rules and templates.
consulting-agents
Use when you need information you don't have, expertise outside your comfort zone, or fresh eyes on code - dispatches agents to research, advise, or review. NOT for implementation delegation (see subagent-driven-development).
domain-review-before-implementation
BEFORE dispatching any implementation agent or starting to code - if you're about to write "Task(subagent_type=..., prompt=...)" for implementation, or about to implement a plan yourself, STOP and review first. The prompt you're about to send IS a brief - review it for design flaws before the agent implements garbage.
spawning-agents-on-the-command-line
Use when subagents need to delegate work but can't use Task tool, or when needing to test skills in isolated context - spawns Claude instances via CLI backgrounding with JSON responses
tracking-technical-debt
Use when you notice code problems while working on something else - links code markers to beads so issues don't get lost. Triggers on "I see a problem but can't fix it now."
antiquities-extractor
Extract and structure data from documents about the illegal antiquities trade, including dealers, collectors, artifacts, locations, and relationships. Use when processing news reports, academic articles, legal documents, encyclopedia entries, or research materials pertaining to looted artifacts, antiquities trafficking, provenance research, or cultural heritage crimes. Returns structured JSON with entities (persons, organizations, artifacts, locations) and their relationships.
agent-builder
Create custom Claude Code sub-agents with specialized expertise and tool access. Use when you need to build reusable agents for specific tasks like code review, debugging, data analysis, or domain-specific workflows.
hooks-manager
Manage Claude Code hooks for workflow automation. Create, configure, test, and debug hooks that execute at various lifecycle points. Supports all hook events (PreToolUse, PostToolUse, SessionStart, etc.) with examples and best practices.
jira
>
skill-builder
Build efficient, scalable Claude Code skills using progressive disclosure and token optimization. Use when creating new skills, optimizing existing skills, or learning skill development patterns. Provides templates, checklists, and working examples.
story-decomposition
Use to break down large stories into optimally-sized stories (1-3 days). Applies PSP measurement discipline.
strangler-pattern-guide
Use as reference guide for strangler pattern implementation. Provides patterns and best practices for legacy migrations.
strangler-pattern
Use when implementing strangler pattern for legacy migrations. Safely migrates controllers with feature flag control.
test-design
Use to design test strategies and create test specifications. Documents testing approaches for stories.
trace-requirements
Use to trace requirements through implementation. Maps acceptance criteria to code and tests.
create-dev-task
Use to generate development task documents for the Dev agent. Creates specifications describing WHAT needs fixing based on validated issues and investigations.
apply-qa-fixes
Use when Dev agent needs to implement fixes based on QA gate results. Reads QA outputs, creates prioritized fix plans, and applies code/test changes to address identified issues.
byos
Create and manage project-level skills shared via git. Skills with prism: metadata are auto-discovered and injected into every PRISM workflow step. Use when teams need project-specific skills available to all agents throughout the workflow.
calibrate-sizing
Use to improve story sizing accuracy by analyzing historical estimation data. Identifies patterns, updates size definitions, and refines PROBE proxy selections.
correct-course
Use when handling sprint changes or scope adjustments. Analyzes change impacts, re-estimates affected stories, and adjusts sprint capacity using PRISM principles.
shared
Shared reference documentation for PRISM skills. Contains common best practices, command patterns, and examples used across multiple skills.
create-epic
Use when creating new Epic documents. Groups related user stories, includes risk analysis, integration points, and story breakdown with PROBE estimation.
create-failing-test
Use to create failing tests before implementing features (TDD approach). Ensures test-first development workflow.
create-next-story
Use to identify and prepare the next logical story based on project progress. Creates comprehensive story files with full technical context.
create-qa-task
Use to create QA task documents. Generates test specifications and validation requirements for QA team.
create-story-tasks
Use to decompose user stories into individual development tasks. Creates task documents that can be assigned, estimated, and tracked.
document-project
Use to analyze and document any project codebase. Creates comprehensive reference documentation for AI-assisted development including architecture and patterns.
execute-checklist
Use to systematically validate documents, stories, or processes against defined checklists. Ensures quality and completeness.
fetch-jira-issue
Use when user mentions a Jira issue key (e.g., PLAT-123) or needs context from Jira. Retrieves and formats issue details for PRISM agent workflows.
file-first
>
init-context
Initialize PRISM .context folder in current project. Use when starting PRISM work in a new project or setting up context management.
initialize-architecture
Use to create complete architecture documentation structure. Creates all required architecture documents from templates.
initialize-project-memory
[DEPRECATED] PRISM-Memory has been archived. This skill is no longer active.
investigate-root-cause
Use for root cause analysis of bugs or issues. Systematically investigates problems to identify underlying causes.
nfr-assess
Use to assess non-functional requirements (security, performance, reliability, maintainability) through E2E integration testing patterns.
prism-loop
Start PRISM TDD workflow loop using Ralph Wiggum pattern. Auto-progresses through Planning, TDD RED (failing tests), TDD GREEN (implementation), and Review phases. Use when user wants to run the core development cycle.
probe-estimation
Use to apply PROBE (PROxy-Based Estimation) method for story sizing. Uses historical data for accurate effort estimation.
Page 1161 of 1445 · 72242 results