Loading...
Loading...
Found 326 Skills
Scaffold or continue a software project with a Harness-style workflow. Use when the user wants a new app or repo, a structured bootstrap, or milestone-driven execution from PRD through implementation. Supports greenfield and existing codebases across web, iOS, CLI, agent, and desktop projects.
Create an AI Evals Pack (eval PRD, test set, rubric, judge plan, results + iteration loop). Use for LLM evaluation, benchmarks, rubrics, error analysis/open coding, and ship/no-ship quality gates for AI features.
Generate structured task lists from specs or requirements. IMPORTANT: After completing ANY spec via ExitSpecMode, ALWAYS ask the user: "Would you like me to generate a task list for this spec?" Use when user confirms or explicitly requests task generation from a plan/spec/PRD.
Remove signs of AI-generated writing from text to make it sound more natural and human-written. Use when editing or reviewing any form of document including: markdown, technical docs, emails, blog posts, PRDs, or any dedicated writing content. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Auto-generate project workflow config (docs/workflow.md) from existing PRD and CLAUDE.md with zero questions. Use when user says "set up workflow", "configure TDD", "wire up dev workflow", or after running /scaffold before /plan. Do NOT use for founder setup (use /init) or project scaffolding (use /scaffold).
Prompt for creating the high-level technical architecture for an Epic, based on a Product Requirements Document.
Guides agents through the first frontend implementation pass from a Google Stitch prototype bundle. Use when the user asks to initialize a frontend project from tech-stack.md, convert design.md/prd.md and Stitch HTML/image prototypes into consistent pages, create mock-data-backed screens with reserved backend API calls, and coordinate every phase with $eliteforge-task-progress-tracker and user confirmations.
The Fifteen-Factor App methodology for modern cloud-native SaaS applications. This skill should be automatically invoked when planning SaaS tools, product software architecture, microservices design, PRPs/PRDs, or cloud-native application development. Extends the original Twelve-Factor App principles with three additional factors (API First, Telemetry, Security). Trigger keywords include "fifteen factor", "12 factor", "SaaS architecture", "cloud-native design", "application architecture", "microservices best practices", or when in a planning/architecture session.
Automatically generate HarmonyOS design documents including architecture design documents and functional design documents based on PRD documents. It analyzes the existing code structure of OpenHarmony before generation to ensure compatibility with the current architecture. Chapter 2 of the architecture design document must be Competitor Solution Analysis, which should be placed after the Requirement Background. Applicable to user requests: (1) Generate architecture design document, (2) Generate functional design document, (3) Generate design document from PRD, (4) Create system architecture design, (5) Write functional specification, (6) Analyze OH code structure. Keywords: architecture design, functional design, design doc, competitor solution analysis, OpenHarmony code analysis, architecture design, functional design, design document generation, OH code analysis, analyze codebase, competitor analysis
Use when converting a design document, PRD, or task list into beads issues - ensures lossless conversion with proper epic hierarchy, validated dependencies for maximum parallelization, and three independent subagent review passes before execution
Authoritative reference for the neo4j-agent-memory Python package — a graph-native memory system for AI agents built on Neo4j — and for the hosted service (NAMS) at memory.neo4jlabs.com. Use this skill whenever the user mentions neo4j-agent-memory, agent memory with Neo4j, context graphs, the POLE+O model, MemoryClient/MemorySettings, the memory MCP server, or any of the framework integrations (LangChain, PydanticAI, CrewAI, AWS Strands, Google ADK, Microsoft Agent Framework, OpenAI Agents, LlamaIndex). Also use when the user mentions the hosted service at memory.neo4jlabs.com, NAMS, the Neo4j Agent Memory Service, the `nams_` API key prefix, or the hosted MCP endpoint. Also use when writing documentation, blog posts, tutorials, PRDs, or code samples for the project, when comparing agent memory approaches, or when positioning graph-native memory against vector-only approaches — even if the user doesn't explicitly name the package.
Use tracer-bullet vertical slices to break down plans, specs, or PRDs into independently assignable issues in the project's issue tracker. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.