Skill Creator
stars-end
44 published skills · 20 GitHub stars across the catalog. View on GitHub ↗
area-context-create
Create codebase area context skills for rapid navigation. MUST BE USED for creating area context skills.Handles ONE-TIME auto-detection with Serena, template-based generation, and manual maintenance.Use when creating new area contexts or regenerating existing ones,or when user mentions "create context skill", "generate area context", "map codebase area",skill generation, codebase navigation, area mapping, or template-based skill creation.
context-admin-ui
Admin dashboard, task management, and review interfaces.
context-analytics
Portfolio analytics, metrics calculation, performance tracking, and dashboard data. Use when working with analytics code, files, or integration. Invoke when navigating analytics codebase, searching for analytics files, debugging analytics errors, or discussing analytics patterns. Keywords: analytics, analytics
context-api-contracts
Frontend-backend API contracts, routes, clients, and type definitions.Handles API endpoint definitions, request/response types, route configuration, and cross-stack integration.Use when working with API endpoints, request/response types, route definitions, or frontend-backend integration,or when user mentions API design, adding endpoints, type mismatches, API contracts, REST endpoints,client integration, "404 Not Found" errors, "Type error" in API calls, or route configuration issues.
context-dx-meta
DX V3 workflow system, skills, slash commands, Beads issue tracking, and Serena code navigation.Handles skill creation, command configuration, workflow automation, and Beads/Serena integration.Use when working with developer workflows, creating skills, configuring commands, or Beads/Serena integration,or when user mentions DX improvements, skill creation, workflow automation, developer experience,"skill not found" errors, "command not working" errors, meta-workflow, DX tooling, or V3 system.
context-infrastructure
Railway deployment, CI/CD workflows, GitHub Actions, and smoke tests.Handles Railway configuration, GitHub Actions workflows, deployment automation, and health checks.Use when working with deployment, CI configuration, Railway setup, or infrastructure automation,or when user mentions Railway environments, GitHub Actions, deployment issues, CI failures,"Build failed" errors, smoke test errors, CI/CD pipelines, Docker configuration, or devops workflows.
context-llm-pipeline
RAG pipeline, embeddings, LLM interactions, and flow orchestration.
context-scrapers
Web scraping spiders (Scrapy), parsers, and source management.
context-security-resolver
Authentication, authorization, Clerk integration, RLS policies, and security patterns. Use when working with security-resolver code, files, or integration. Invoke when navigating security-resolver codebase, searching for security-resolver files, debugging security-resolver errors, or discussing security-resolver patterns. Keywords: security-resolver, {{KEYWORDS}}
context-testing-infrastructure
Tiered testing strategy (UI mock, auth stub, full-stack), fixtures, mocks, and test configuration.Handles test setup, Playwright E2E tests, pytest backend tests, mocking strategies, and CI test configuration.Use when working with tests, test setup, mocking strategies, or CI test configuration,or when user mentions test patterns, auth stub, fixture loaders, Playwright tests, test failures,tiered testing, UI mock, E2E tests, pytest, vitest, or debugging test issues.
context-ui-design
UI theme system, design tokens, Material-UI patterns, and accessibility standards.Handles theme customization, component styling, design system patterns, and accessibility features.Use when working with UI components, theme customization, design system patterns, or accessibility features,or when user mentions Material-UI, MUI components, theme tokens, dark mode, component styling,design system, accessibility, layout issues, styling problems, or ARIA patterns.
docs-create
Create epic-specific documentation skill with external reference docs. MUST BE USED for caching external docs.Fetches URLs, caches full content, uses documentation-engineer to generate cohesive summaries, and creates auto-activating skill.Use when starting work on epic that requires external documentation context (API docs, tool guides, reference materials),or when user mentions "cache docs", "external docs", "API documentation", URLs for docs,documentation needs, reference materials, knowledge caching, or epic context documentation.
finish-feature
Complete epic with cleanup and archiving, or verify feature already closed. MUST BE USED when finishing epics/features.For epics: Verifies children closed, archives docs, caches to Serena, closes epic.For features/tasks/bugs: Verifies already closed (from PR creation), archives docs, caches to Serena.Non-epic issues must be closed at PR creation time (atomic merge pattern).Use when user says "I'm done with this epic", "finish the feature", "finish this epic", "archive this epic",or when user mentions epic completion, cleanup, archiving, feature finalization, or closing work.
fix-pr-feedback
Address PR feedback with iterative refinement. MUST BE USED when fixing PR issues.Supports auto-detection (CI failures, code review) and manual triage (user reports bugs). Creates Beads issues for all problems, fixes systematically.Use when user says "fix the PR", "i noticed bugs", "ci failures", or "codex review found issues",or when user mentions CI failures, review comments, failing tests, PR iterations,bug fixes, feedback loops, or systematic issue resolution.
issue-first
Enforce Issue-First pattern by creating Beads tracking issue BEFORE implementation. MUST BE USED for all implementation work.Classifies work type (epic/feature/task/bug/chore), determines priority (0-4), finds parent in hierarchy, creates issue, then passes control to implementation.Use when starting implementation work,or when user mentions "no tracking issue", "missing Feature-Key", work classification,creating features, building new systems, beginning development, or implementing new functionality.
lint-check
Run quick linting checks on changed files. MUST BE USED when user wants to check code quality.Fast validation (<5s) following V3 trust-environments philosophy.Use when user says "lint my code", "check formatting", or "run linters",or when user mentions uncommitted changes, pre-commit state, formatting issues,code quality, style checks, validation, prettier, eslint, pylint, or ruff.
merge-pr
Prepare PR for merge and guide human to merge via GitHub web UI. MUST BE USED when user wants to merge a PR.Verifies CI passing, verifies Beads issue already closed (from PR creation), and provides merge instructions.Issue closure happens at PR creation time (create-pull-request skill), NOT at merge time.Use when user says "merge the PR", "merge it", "merge this", "ready to merge", "merge to master",or when user mentions CI passing, approved reviews, ready-to-merge state, ready to ship,merge, deployment, PR completion, or shipping code.
parallelize-cloud-work
Delegate independent work to Claude Code Web cloud sessions for parallel execution. Generates comprehensive session prompts with context exploration guidance, verifies Beads state, provides tracking commands. Use when user says "parallelize work to cloud", "start cloud sessions", or needs to execute multiple independent tasks simultaneously, or when user mentions cloud sessions, cloud prompts, delegate to cloud, Claude Code Web, generate session prompts, parallel execution, or asks "how do I use cloud sessions".
session-end
End Claude Code session with Beads sync and summary. MUST BE USED when user says they're done, ending session, or logging off.Guarantees Beads export to git, shows session stats, and suggests next ready work. Handles cleanup and context saving.Use when user says "goodbye", "bye", "done for now", "logging off",or when user mentions end-of-session, session termination, cleanup, context saving,bd sync, or export operations.
skill-creator
Create new Claude Code skills following V3 DX patterns with Beads/Serena integration. MUST BE USED when creating skills.Follows tech lead proven patterns from 300k LOC case study.Use when user wants to create a new skill, implement workflow automation, or enhance the skill system,or when user mentions "need a skill for X", "automate this workflow", "create new capability",repetitive manual processes, skill creation, meta-skill, or V3 patterns.
beads-guard
Safe Beads workflow helper (warning-only). Use before bd sync/close/create toavoid JSONL conflicts. Ensures you are on a feature branch, up to date withorigin/master, and stages Beads files cleanly with Feature-Key commits.
beads-workflow
Beads issue tracking and workflow management with automatic git branch creation. MUST BE USED for Beads operations.Handles full epic→branch→work lifecycle, dependencies, and ready task queries.Use when creating epics/features (auto-creates branch), tracking work, finding ready issues, or managing dependencies,or when user mentions "create issue", "track work", "bd create", "find ready tasks",issue management, dependencies, work tracking, or Beads workflow operations.
context-database-schema
Supabase PostgreSQL schema management, 86+ migrations, RLS policies, and type generation.Handles table creation, schema changes, migrations, foreign key constraints, and migration workflows.Use when working with database schema, migrations, data modeling, or type definitions,or when user mentions database changes, table modifications, schema updates, migration failures,"relation does not exist" errors, foreign key issues, Supabase schema operations, users table, accounts table, or holdings table.
create-pull-request
Create GitHub pull request with atomic Beads issue closure. MUST BE USED for opening PRs.Asks if work is complete - if YES, closes Beads issue BEFORE creating PR (JSONL merges atomically with code).If NO, creates draft PR with issue still open. Automatically links Beads tracking and includes Feature-Key.Use when user wants to open a PR, submit work for review, merge into master, or prepare for deployment,or when user mentions "ready for review", "create PR", "open PR", "merge conflicts", "CI checks needed","branch ahead of master", PR creation, opening pull requests, deployment preparation, or submitting for team review.