Browse Skills

grey-haven-performance-optimization.md

15

1 export grey-haven-performance-optimization

2 from "greyhaven-ai/claude-code-config"

3 Comprehensive performance analysis and optimization for algorithms (O(n²)→O(n)), databases (N+1 queries, indexes), React (memoization, virtual lists), bundles (code splitting), API caching, and memory leaks. 85%+ improvement rate. Use when application is slow, response times exceed SLA, high CPU/memory usage, performance budgets needed, or when user mentions 'performance', 'slow', 'optimization', 'bottleneck', 'speed up', 'latency', 'memory leak', or 'performance tuning'.

2026-01-21

grey-haven-project-scaffolding.md

15

1 export grey-haven-project-scaffolding

2 from "greyhaven-ai/claude-code-config"

3 Generate production-ready project scaffolds for Grey Haven stack with Cloudflare Workers, React + TypeScript, Python + Pydantic, PlanetScale, proper structure, and configuration. Use when starting new projects, creating microservices, setting up monorepo workspaces, initializing projects, or when user mentions 'new project', 'project scaffold', 'project template', 'project setup', 'bootstrap project', 'project starter', or 'initialize project'.

2026-01-21

plugin-authoring.md

15

1 export plugin-authoring

2 from "ivan-magda/claude-code-plugin-template"

3 Use when creating, modifying, or debugging Claude Code plugins. Triggers on .claude-plugin/, plugin.json, marketplace.json, commands/, agents/, skills/, hooks/ directories. Provides schemas, templates, validation workflows, and troubleshooting.

2026-01-20

rails-ai:styling.md

15

1 export rails-ai:styling

2 from "zerobearing2/rails-ai"

3 Use when styling Rails views - Tailwind CSS utility-first framework and DaisyUI component library with theming

2026-01-20

grey-haven-documentation-alignment.md

15

1 export grey-haven-documentation-alignment

2 from "greyhaven-ai/claude-code-config"

3 6-phase verification system ensuring code matches documentation with automated alignment scoring (signature, type, behavior, error, example checks). Reduces onboarding friction 40%. Use when verifying code-docs alignment, onboarding developers, after code changes, pre-release documentation checks, or when user mentions 'docs out of sync', 'documentation verification', 'code-docs alignment', 'docs accuracy', 'documentation drift', or 'verify documentation'.

2026-01-21

premortem.md

15

1 export premortem

2 from "Everplay-Tech/pewpew"

3 Prospective hindsight. Use pm: to assume failure has already happened and work backward to identify causes. Gary Klein's method for surfacing risks and blind spots.

2026-01-05

API Design.md

15

1 export API Design

2 from "yaleh/meta-cc"

3 Systematic API design methodology with 6 validated patterns covering parameter categorization, safe refactoring, audit-first approach, automated validation, quality gates, and example-driven documentation. Use when designing new APIs, improving API consistency, implementing breaking change policies, or building API quality enforcement. Provides deterministic decision trees (5-tier parameter system), validation tool architecture, pre-commit hook patterns. Validated with 82.5% cross-domain transferability, 37.5% efficiency gains through audit-first refactoring.

2025-12-13

grey-haven-code-style.md

15

1 export grey-haven-code-style

2 from "greyhaven-ai/claude-code-config"

3 Apply Grey Haven Studio's TypeScript/React and Python/FastAPI coding standards from production templates. Use when writing code, reviewing PRs, fixing linting errors, formatting files, or when the user mentions 'code standards', 'Grey Haven style', 'linting', 'Prettier', 'ESLint', 'Ruff', 'formatting rules', or 'coding conventions'. Includes exact Prettier/ESLint/Ruff configs, naming conventions, project structure, and multi-tenant database patterns.

2026-01-21

Technical Debt Management.md

15

1 export Technical Debt Management

2 from "yaleh/meta-cc"

3 Systematic technical debt quantification and management using SQALE methodology with value-effort prioritization, phased paydown roadmaps, and prevention strategies. Use when technical debt unmeasured or subjective, need objective prioritization, planning refactoring work, establishing debt prevention practices, or tracking debt trends over time. Provides 6 methodology components (measurement with SQALE index, categorization with code smell taxonomy, prioritization with value-effort matrix, phased paydown roadmap, trend tracking system, prevention guidelines), 3 patterns (SQALE-based quantification, code smell taxonomy mapping, value-effort prioritization), 3 principles (high-value low-effort first, SQALE provides objective baseline, complexity drives maintainability debt). Validated with 4.5x speedup vs manual approach, 85% transferability across languages (Go, Python, JavaScript, Java, Rust), SQALE industry-standard methodology.

2025-12-13

rails-ai:security.md

15

1 export rails-ai:security

2 from "zerobearing2/rails-ai"

3 CRITICAL - Use when securing Rails applications - XSS, SQL injection, CSRF, file uploads, command injection prevention

2026-01-20

refactor.md

15

1 export refactor

2 from "ujuc/dotrc"

3 Suggests and performs code refactoring following best practices. Use when user asks to "리팩토링 해줘", "refactor this", "코드 개선해줘", "정리해줘", "클린 코드로", "중복 제거해줘", "이거 더 깔끔하게", or wants to improve code quality without changing functionality.

2026-01-12

interview.md

15

1 export interview

2 from "panaversity/claude-code-skills-lab"

3 This skill conducts discovery conversations to understand user intent and agree on approach before taking action. It should be used when the user explicitly calls /interview, asks for recommendations, needs brainstorming, wants to clarify, or when the request could be misunderstood. Prevents building the wrong thing by uncovering WHY behind WHAT.

2026-01-05

rails-ai:views.md

15

1 export rails-ai:views

2 from "zerobearing2/rails-ai"

3 Use when building Rails view structure - partials, helpers, forms, nested forms, accessibility (WCAG 2.1 AA)

2026-01-20

grey-haven-onboarding-coordination.md

15

1 export grey-haven-onboarding-coordination

2 from "greyhaven-ai/claude-code-config"

3 Automate developer onboarding with personalized plans, Linear integration, knowledge base setup, and milestone tracking. Use when onboarding new developers, planning team expansion, or managing role transitions.

2026-01-21

grey-haven-deployment-cloudflare.md

15

1 export grey-haven-deployment-cloudflare

2 from "greyhaven-ai/claude-code-config"

3 Deploy TanStack Start applications to Cloudflare Workers/Pages with GitHub Actions, Doppler, Wrangler, database migrations, and rollback procedures. Use when deploying Grey Haven applications.

2026-01-21

grey-haven-testing-strategy.md

15

1 export grey-haven-testing-strategy

2 from "greyhaven-ai/claude-code-config"

3 Grey Haven's comprehensive testing strategy - Vitest unit/integration/e2e for TypeScript, pytest markers for Python, >80% coverage requirement, fixture patterns, and Doppler for test environments. Use when writing tests, setting up test infrastructure, running tests, debugging test failures, improving coverage, configuring CI/CD, or when user mentions 'test', 'testing', 'pytest', 'vitest', 'coverage', 'TDD', 'test-driven development', 'unit test', 'integration test', 'e2e', 'end-to-end', 'test fixtures', 'mocking', 'test setup', 'CI testing'.

2026-01-21

Testing Strategy.md

15

1 export Testing Strategy

2 from "yaleh/meta-cc"

3 Systematic testing methodology for Go projects using TDD, coverage-driven gap closure, fixture patterns, and CLI testing. Use when establishing test strategy from scratch, improving test coverage from 60-75% to 80%+, creating test infrastructure with mocks and fixtures, building CLI test suites, or systematizing ad-hoc testing. Provides 8 documented patterns (table-driven, golden file, fixture, mocking, CLI testing, integration, helper utilities, coverage-driven gap closure), 3 automation tools (coverage analyzer 186x speedup, test generator 200x speedup, methodology guide 7.5x speedup). Validated across 3 project archetypes with 3.1x average speedup, 5.8% adaptation effort, 89% transferability to Python/Rust/TypeScript.

2025-12-13

rails-ai:testing.md

15

1 export rails-ai:testing

2 from "zerobearing2/rails-ai"

3 Use when testing Rails applications - TDD, Minitest, fixtures, model testing, mocking, test helpers

2026-01-20

rails-ai:mailers.md

15

1 export rails-ai:mailers

2 from "zerobearing2/rails-ai"

3 Use when sending emails - ActionMailer with async delivery via SolidQueue, templates, previews, and testing

2026-01-20

review.md

15

1 export review

2 from "ujuc/dotrc"

3 Performs code review following team's quality assurance guidelines. Use when the user asks to "review code", "check this code", "리뷰해줘", "코드 리뷰", "코드 검토", "이 코드 봐줘", "이거 괜찮아?", "확인해줘", "문제 없어?", or after writing code when they want feedback on the changes just made.

2026-01-12

grey-haven-memory-systems.md

15

1 export grey-haven-memory-systems

2 from "greyhaven-ai/claude-code-config"

3 Design and implement long-term memory systems for AI agents using vector stores, knowledge graphs, and hybrid approaches. Includes benchmarks and decision frameworks. Use when building persistent agent memory, implementing RAG, designing knowledge bases, or when user mentions 'memory', 'RAG', 'vector store', 'knowledge graph', 'long-term memory', 'retrieval', or 'embeddings'.

2026-01-21

design-skill.md

15

1 export design-skill

2 from "uxjoseph/ppt_team_agent"

3 프레젠테이션 슬라이드를 미려한 HTML로 디자인. 슬라이드 HTML 생성, 시각적 디자인, 레이아웃 구성이 필요할 때 사용.

2026-01-21

dependency-analyzer.md

15

1 export dependency-analyzer

2 from "lis186/SourceAtlas"

3 Analyze dependencies for upgrade planning and migration. Use when user asks "upgrade to X", "migrate from X to Y", "what breaks if we upgrade", "iOS 17 migration", "React 18 upgrade", or planning framework/SDK upgrades.

2026-01-18

grey-haven-tdd-typescript.md

15

1 export grey-haven-tdd-typescript

2 from "greyhaven-ai/claude-code-config"

3 TypeScript/JavaScript Test-Driven Development with Vitest, strict red-green-refactor methodology, React component testing, and comprehensive coverage patterns. Use when implementing TypeScript features with TDD, writing Vitest tests, testing React components, developing with test-first approach, or when user mentions 'TypeScript TDD', 'Vitest', 'React testing', 'JavaScript TDD', 'red-green-refactor', 'TypeScript unit tests', or 'test-driven TypeScript'.

2026-01-21