Architecture & codebase
12,717 rows, by stacks then stars
1,011 of these skill files have been read, by 858 distinct authors, and what they tell an agent counted. What Architecture & codebase authors agree on, and what they forbid
staksoft/magento-claude-skills/skills/magento-module Skill
6★ repoCorrect Magento 2 / Mage-OS / Adobe Commerce module development: scaffolding new modules, extending or customizing core behavior (plugin vs observer vs preference decisions), declarative schema and custom tables, product/EAV attributes, dependency injection, checkout/cart/totals and custom order or shipping fee logic, admin configuration (system.xml/ACL), admin grids and ui_components, layout XML and view models, upgrading or migrating custom modules (incl. to Mage-OS) and their composer.json constraints, and debugging playbooks for setup:di:compile failures, layout not applying, and observers/plugins that don't fire. Use this skill whenever the user is writing, modifying, or debugging custom Magento, Mage-OS, or Adobe Commerce code — creating or extending a module/extension, intercepting core behavior, adding database tables or attributes, building admin settings or grids, frontend blocks or templates, or fixing errors from bin/magento commands — even if they don't say "module" explicitly. Strong triggers: "how do I override X in Magento", "my Magento layout/plugin/observer isn't working", "do I use an observer or a plugin", or anything touching app/code, di.xml, events.xml, db_schema.xml, or layout XML. Do NOT trigger for storefront performance/cache audits (use the magento-audit skill), buying or recommending third-party extensions, operational admin tasks (creating coupons, importing product CSVs, session/login settings), Magento hosting/sizing questions, content/SEO copy, or non-Magento platforms like Shopify or WooCommerce.
maxwellokumu/okaudit-claude-skills/network-security/network-config-reviewer Skill
no license6★ repoReview firewall and network rule sets for overly permissive access, risky exposure, and other configuration weaknesses so Claude can explain the highest-priority findings clearly.
jeffsenso/prestashop-skills/skills/prestashop-module-development/ps9-core-ai/Component/Javascript/skills/init-grid-extensions Skill
6★ repoEnable JavaScript grid extensions for a listing page. Extensions add sorting, filtering, bulk actions, column toggling, position reordering, and other interactive behaviors to the grid. Trigger: "add grid extensions for {Domain}", "enable grid extensions for {Domain}", "initialize grid JS for {Domain}".
jeffsenso/prestashop-skills/skills/prestashop-module-development/ps9-core-ai/Component/Javascript/skills/init-js-components Skill
6★ repoInitialize and use PrestaShop's global JS components via initComponents(). Covers TranslatableInput, ChoiceTree, TinyMCEEditor, TaggableField, and all other available components. Components activate based on data-* attributes in the DOM. Trigger: "initialize components for {Domain}", "enable components for {Domain}", "add components to {Domain} form".
Activation onboarding playbook
deciqAI/knowledge-skills/activation-onboarding-playbook Skill
6★ repoActivate when: signups don't turn into active/paying users; 'people sign up but don't stick', designing onboarding, improving activation; aha moment, time-to-value. Do NOT activate when: the problem is acquisition (no signups) or long-term retention of already-activated users (different lever). More: deciqai.com/s/activation-onboarding-playbook
deciqAI/knowledge-skills/trust-brand-architecture Skill
6★ repoActivate when: brand perception lags product quality; a values campaign generated backlash ('they say X but do Y'); NPS and brand sentiment diverge; marketing underperforms despite a good product; someone asks 'how do we build brand trust?' or 'why isn't our marketing working?'. Do NOT activate when: a single catastrophic event requires immediate legal or crisis-communication response first; the product genuinely does not work and needs engineering fixes before trust is addressed. More: deciqai.com/s/trust-brand-architecture
seandavi/scriptorium/skills/init Skill
6★ repoConversationally bootstrap MANUSCRIPT_STATE.yaml for a new or existing manuscript directory. Infers what it can from the filesystem (title, sections, bibliography paths) and asks the author about the subjective fields (core_claims, known_weaknesses, terminology, audience). Validates against the JSON Schema before writing. Invoke when the user wants to set up scriptorium on a manuscript that does not yet have — or has only a partial — MANUSCRIPT_STATE.yaml.
Rudra-ravi/frida-skills/frida-gadget-injection Skill
6★ repoPlan and troubleshoot Frida Gadget workflows for Android, iOS, desktop apps, jailed devices, embedded Gadget configuration, load timing, code-signing constraints, and script or interaction mode setup.
Rudra-ravi/frida-skills/frida-setup-checklist Skill
6★ repoPrepare and verify a Frida environment, including host tools, Android frida-server, iOS setup, USB or remote transport, version matching, and smoke tests.
idaibin/skills/skills/repo-map Skill
6★ repoIndependent Agent Skills for repository analysis, planning, implementation, review, delivery, design, and runtime verification.
loremaster-ai/loremaster/skills/loremaster-setup Skill
6★ repoGuided, interactive onboarding that takes a Hermes Agent user from "tap added" to "first project live" — run it on first install of the Loremaster pack, when adding a new project (new channel + new lore vault), or when reconfiguring an existing setup (scripts, Jira, timezone, Obsidian).
PatterAI/skills/setup-patter Skill
6★ repoInstall the Patter voice/telephony SDK (Python or TypeScript) and configure the provider and carrier API keys required for real phone calls. Use when the user is starting a new Patter project, hitting "missing API key" errors, setting up Twilio or Telnyx, integrating OpenAI Realtime / ElevenLabs / Deepgram, or asking how to get Patter running — even if they don't explicitly say "setup" or "credentials". Covers Patter 0.7.0 in both Python (>=3.11) and TypeScript (Node >=20) runtimes.
JordanCoin/ios-skills-collection/skills/andrewgleave--cleanse Skill
no license6★ repoReview code for readability, then simplify it to be easy to follow and understand. Use this skill when the user wants to simplify code, improve readability, clean up for handoff, make code skimmable, reduce complexity, refactor for clarity, strip boilerplate, prepare code for future maintainers, or make a codebase easier to pick up. Trigger liberally — any request touching readability, simplification, cleanup, or "make this easier to understand" should use this skill. Also trigger when the user says things like "review this", "clean this up", "tidy this", "make this simpler", "reduce complexity", "flatten this", "strip the noise", or "I want to understand this code quickly next time I open it".
JordanCoin/ios-skills-collection/skills/arimunandar--vip-architecture Skill
no license6★ repoVIP+W (View-Interactor-Presenter-Worker) Clean Architecture for iOS with unidirectional data flow and proper separation of concerns
The same file is in 1 other repository
Dimillian orchestrate batch refactor
JordanCoin/ios-skills-collection/skills/dimillian--orchestrate-batch-refactor Skill
no license6★ repoPlan and execute large refactor or rewrite efforts efficiently with parallel multi-agent analysis and implementation. Use when a user asks to refactor many files, split workstreams, analyze a target code area, and coordinate sub-agents with clear ownership and dependency-aware execution.
The same file is in 11 other repositories
Dimillian review and simplify changes
JordanCoin/ios-skills-collection/skills/dimillian--review-and-simplify-changes Skill
no license6★ repoReview a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes. Use when the user asks to "simplify code", "review changed code", "check for code reuse", "review code quality", "review efficiency", "simplify changes", "clean up code", "refactor changes", or "run simplify".
Dimillian swiftui view refactor
JordanCoin/ios-skills-collection/skills/dimillian--swiftui-view-refactor Skill
no license6★ repoRefactor and review SwiftUI view files with strong defaults for small dedicated subviews, MV-over-MVVM data flow, stable view trees, explicit dependency injection, and correct Observation usage. Use when cleaning up a SwiftUI view, splitting long bodies, removing inline actions or side effects, reducing computed `some View` helpers, or standardizing `@Observable` and view model initialization patterns.
JordanCoin/ios-skills-collection/skills/dpearson2699--app-clips Skill
no license6★ repoBuild iOS App Clips with invocation URLs, NFC, QR codes, App Clip Codes, Safari banners, Maps, Messages, and shared App Group data handoff to the full app. Covers target setup, experience configuration, size limits, NSUserActivity handling, SKOverlay promotion, location confirmation, and capability limits. Use when creating App Clips or wiring App Clip invocation and full-app migration.
Efremidze swift architecture skill
JordanCoin/ios-skills-collection/skills/efremidze--swift-architecture-skill Skill
no license6★ repoSwift architecture patterns and playbooks for MVVM, TCA, Clean Architecture, and more.
Erikote04 swift api design guidelines skill
JordanCoin/ios-skills-collection/skills/erikote04--swift-api-design-guidelines-skill Skill
no license6★ repoWrite, review, or improve Swift APIs using Swift API Design Guidelines for naming, argument labels, documentation comments, terminology, and general conventions. Use when designing new APIs, refactoring existing interfaces, or reviewing API clarity and fluency.
Eronred onboarding optimization
JordanCoin/ios-skills-collection/skills/eronred--onboarding-optimization Skill
no license6★ repoWhen the user wants to improve their app's onboarding experience, increase activation rate, reduce Day 1 drop-off, or optimize the first-run flow. Use when the user mentions "onboarding", "first-run", "activation", "tutorial", "day 1 retention", "new user flow", "permission prompts", "sign-up conversion", "onboarding funnel", or "users dropping off early". For overall retention strategy, see retention-optimization. For paywall placement, see monetization-strategy.
The same file is in 2 other repositories
Rudrankriyam asc signing setup
JordanCoin/ios-skills-collection/skills/rudrankriyam--asc-signing-setup Skill
no license6★ repoSet up bundle IDs, capabilities, signing certificates, provisioning profiles, and encrypted signing sync with the asc cli. Use when onboarding a new app, rotating signing assets, or sharing them across a team.
ldilov/harness-forge/skills/cloud-architect Skill
6★ repoCloud architecture guidance for platform design, deployment topology, reliability, security, observability, and cost trade-offs.
ldilov/harness-forge/skills/hforge-init Skill
6★ repoinitialize harness forge in the current repository, bootstrap the target-aware runtime, and establish the managed surfaces needed for later review, analysis, and decision tracking. use when the repo is not initialized, when runtime files are missing, or when the user asks to set up hforge in a project.
ldilov/harness-forge/skills/repo-onboarding Skill
6★ reporepository discovery, entrypoint mapping, and fast onboarding for unfamiliar codebases. use when the repo is new, mixed, legacy, monorepo-shaped, poorly documented, or when the next safe step is blocked on understanding layout, ownership, and commands.
ldilov/harness-forge/.agents/skills/speckit-git-initialize Skill
6★ repoInitialize a Git repository with an initial commit
ldilov/harness-forge/skills/engineering-assistant Skill
6★ repoarchitecture and implementation orchestrator for cross-cutting engineering work. use when a task needs system design, code architecture, refactoring strategy, implementation planning, specialist-skill routing, or explicit project-memory and change-discipline guidance in one surface.
ldilov/harness-forge/skills/observability-setup Skill
6★ repoDefine local-first logging, metrics, and diagnostic signals for a runtime surface.
zenml-io/skills/skills/zenml-quick-wins/skills/quick-wins Skill
6★ repoImplements ZenML quick wins to enhance MLOps workflows. Investigates codebase and stack configuration, recommends high-priority improvements, and implements metadata logging, experiment tracking, alerts, scheduling, secrets management, tags, git hooks, HTML reports, Model Control Plane setup, live streaming events, lifecycle hooks, and resource-pool-aware step requests. Use when: user wants to improve their ZenML setup, asks about MLOps best practices, mentions "quick wins", wants to enhance pipelines, or needs help with ZenML features like experiment tracking, alerting, scheduling, or model governance.
jph4cks/redhound-arsenal/spiderfoot Skill
6★ repoBuild, extend, and operate SpiderFoot — an OSINT automation platform with 200+ modules for passive and active reconnaissance. Use when the user needs automated intelligence gathering on IP addresses, domains, email addresses, phone numbers, usernames, subnets, or ASNs. Covers installation, web UI and CLI operation, scan types, module configuration, API key setup, correlation engine, data visualization, export formats, and OSINT investigation methodology for penetration testing and threat intelligence engagements.
jph4cks/redhound-arsenal/subfinder Skill
6★ repoUse and operate Subfinder — a fast passive subdomain enumeration tool by ProjectDiscovery that queries dozens of passive DNS data sources simultaneously. Use when performing subdomain discovery during recon, configuring API keys for maximum source coverage, integrating passive enumeration into recon pipelines with httpx and nuclei, or chaining with active tools for full-spectrum recon-to-exploit workflows. Covers installation, all flags, provider-config.yaml setup with all supported API key providers, output formats, recursive enumeration, rate limiting, silent mode, stdin/stdout piping, and complete pipeline integration. GitHub: https://github.com/projectdiscovery/subfinder (13.4k stars).
LuckyOneTwoThree/pm-skill/pm-06-growth/skills/activation-onboarding Skill
no license6★ repo当需要优化用户Onboarding流程时使用。Onboarding自动优化Pipeline,分析Onboarding数据和用户分群,自动生成个性化引导策略,设计A/B测试方案。关键词:Onboarding、新用户引导、引导优化、个性化引导、用户激活、新手引导、上手快、引导太长。
athal7/dotfiles/skills/chezmoi Skill
no license6★ repoManage dotfiles via chezmoi — apply safely, destroy files, manage LaunchAgents and externals, config and template gotchas
athal7/dotfiles/skills/code-quality Skill
no license6★ repoLoad when reviewing a diff, naming a code smell or anti-pattern, deciding refactoring direction, or grading review-comment severity. Required reading when a named pattern is cited — load explicitly rather than paraphrasing from memory.
ucsahinn/codex-chef/plugins/codex-chef-workflows/skills/codex-chef-operator Skill
6★ repoMaintain, audit, and improve Codex Chef setup repositories. Use for README/docs/template/catalog/installer/validation updates, release-readiness work, and safe Codex starter maintenance without weakening security, leaking local state, or changing external systems.
Unique-Divine/jiyuu/ai-skills/nibiru-cli-nibid Skill
6★ repoQuery Nibiru chain state and submit transactions with the `nibid` CLI, including setup via `ud`, config inspection, key discovery with `nibid keys list`, bank transfers, bank balance queries, EVM multi-VM balance checks such as `nibid q evm balance` for Sai USDC, wasm contract queries, wasm execute/instantiate flows, and transaction lookups by hash. Use when the user mentions `nibid`, Nibiru CLI, `nibid keys list`, `--from`, `nibid tx bank`, `nibid tx wasm`, `nibid q bank`, `nibid q evm balance`, `nibid q wasm`, `nibid q tx`, balances, contract-state smart, or tx hashes.
Unique-Divine/jiyuu/ai-skills/repo-map Skill
6★ repoMaps and routes between key repositories on my machine (boku, nibi-chain, nibi-geth, nibi-go-hm, nibi-ts-sdk, sai-website, sai-perps, nibi-iac, nibi-home-site, gh-io-ud, wasm-cosmwasm, wasm-go-wasmvm). Use when the user asks which repo to look at, where a feature lives, how repos connect, how services are deployed (Terraform/IaC), when a task spans chain, EVM, indexer, SDK, frontend, and docs, or when the user asks about the personal site, blog posts, official Nibiru docs, or Astro/gh-pages.
DanielC000/loom/packages/daemon/assets/skills/setup-assistant Skill
6★ repoThe operating doctrine for the Loom Platform operator — a friendly, user-facing workspace operator that gets a brand-new user set up and helps maintain their workspace thereafter. Load at the start of any setup-assistant session to help the user create, configure, and archive projects, define agents and profiles, pick default skills and a workflow, and act on their behalf over the curated loom-setup tool surface — confirming big or irreversible actions first. NOT a self-improving Platform Lead.
HK-hub/AgentSkills/api-design-principles Skill
6★ repoMaster REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
The same file is in 1 other repository
HK-hub/AgentSkills/api-design Skill
6★ repoProfessional API design skill covering RESTful APIs, GraphQL, API versioning, authentication, idempotency, and API documentation best practices. Use this skill when designing RESTful APIs, creating GraphQL schemas, implementing API versioning strategies, or need guidance on authentication, error handling, and API documentation.
The same file is in 1 other repository
HK-hub/AgentSkills/architecture-designer Skill
6★ repoUse when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.
The same file is in 1 other repository
HK-hub/AgentSkills/architecture-patterns Skill
6★ repoImplement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.
The same file is in 4 other repositories
HK-hub/AgentSkills/design-pattern Skill
6★ repoExpert knowledge in software design patterns covering GoF patterns, architectural patterns, and modern design principles. Apply appropriate patterns to improve code maintainability, scalability, and extensibility. Use this skill when designing new software components, refactoring existing code, reviewing code for design quality, resolving complex design problems, or need guidance on applying SOLID principles and identifying code smells.
The same file is in 1 other repository
HK-hub/AgentSkills/fullstack-dev Skill
6★ repoFull-stack backend architecture and frontend-backend integration guide. TRIGGER when: building a full-stack app, creating REST API with frontend, scaffolding backend service, building todo app, building CRUD app, building real-time app, building chat app, Express + React, Next.js API, Node.js backend, Python backend, Go backend, designing service layers, implementing error handling, managing config/auth, setting up API clients, implementing auth flows, handling file uploads, adding real-time features (SSE/WebSocket), hardening for production. DO NOT TRIGGER when: pure frontend UI work, pure CSS/styling, database schema only.
The same file is in 6 other repositories
HK-hub/AgentSkills/graphql-architect Skill
6★ repoUse when designing GraphQL schemas, implementing Apollo Federation, or building real-time subscriptions. Invoke for schema design, resolvers with DataLoader, query optimization, federation directives.
The same file is in 2 other repositories
HK-hub/AgentSkills/java-architect Skill
6★ repoUse when building, configuring, or debugging enterprise Java applications with Spring Boot 3.x, microservices, or reactive programming. Invoke to implement WebFlux endpoints, optimize JPA queries and database performance, configure Spring Security with OAuth2/JWT, or resolve authentication issues and async processing challenges in cloud-native Spring applications.
The same file is in 2 other repositories
HK-hub/AgentSkills/microservices-architect Skill
6★ repoDesigns distributed system architectures, decomposes monoliths into bounded-context services, recommends communication patterns, and produces service boundary diagrams and resilience strategies. Use when designing distributed systems, decomposing monoliths, or implementing microservices patterns — including service boundaries, DDD, saga patterns, event sourcing, CQRS, service mesh, or distributed tracing.
The same file is in 2 other repositories
HK-hub/AgentSkills/plugin-structure Skill
6★ repoThis skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.
The same file is in 9 other repositories
HK-hub/AgentSkills/spring-boot-engineer Skill
6★ repoGenerates Spring Boot 3.x configurations, creates REST controllers, implements Spring Security 6 authentication flows, sets up Spring Data JPA repositories, and configures reactive WebFlux endpoints. Use when building Spring Boot 3.x applications, microservices, or reactive Java applications; invoke for Spring Data JPA, Spring Security 6, WebFlux, Spring Cloud integration, Java REST API design, or Microservices Java architecture.
The same file is in 2 other repositories
HK-hub/AgentSkills/teach-impeccable Skill
6★ repoOne-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
Mozurok/fhorja.dev/.claude/skills/api-contract-review Skill
6★ repoReview an API contract (endpoints, request/response shapes, error codes, auth model) BEFORE implementation for naming consistency, versioning, pagination, idempotency, and alignment with existing endpoints. Distinct from review-hard (post-implementation risk) and repo-consistency-sweep (pattern matching on written code). Use when designing new endpoints or modifying existing API contracts. Do not use when the API is already implemented (use review-hard or repo-consistency-sweep instead).
Mozurok/fhorja.dev/.claude/skills/backend-system-design Skill
6★ repoProduce a staff-grade backend system-design RFC for the active task: a 12-section design document (problem, requirements, architecture, data model and storage, API contract, caching, scaling and bottlenecks, reliability and SLOs, security, observability, rollout and migration, trade-offs) for a new service, endpoint, or backend feature, persisted as BACKEND_SYSTEM_DESIGN.md. Capability-routed, not stack-specific; composes with slo-define, performance-budget, api-contract-review, and release-plan rather than duplicating them. Use when a backend service or feature needs an architecture-level design before planning and slicing. Do not use to slice an already-designed change (use implementation-plan), to analyze blast radius (use impact-analysis), to review an API contract in isolation (use api-contract-review), to design the frontend surface (use frontend-system-design), or with no active task folder (run task-init first).
Mozurok/fhorja.dev/.claude/skills/color-contrast-architect Skill
6★ repoSenior design-system color contrast architect enforcing WCAG 2.2 AA/AAA per design context (normal text, large text, UI components, focus indicators). Audits every documented foreground and background pair across light and dark themes BEFORE the visual choices lock, producing a pairwise contrast matrix with token-level remediation. Activates when design-bootstrap proposes color tokens without contrast pairs, when DECISIONS.md proposes a primary or accent color without confirming contrast, when foundations/color.md exists without a contrast matrix, or when a screen-spec or component-spec mentions an unvalidated pair. Do not use for a single pair (use component-spec inline), when the design system has no theme variants, when no accessibility target is locked (raise via decision-interview first), or after remediation is agreed (use implement-approved-slice).
Mozurok/fhorja.dev/.claude/skills/design-bootstrap Skill
6★ repoBootstrap a design system from a Figma file using MCP tools. Extracts token variables, identifies components, creates the directory structure, and generates scaffolded foundation docs and a component inventory. Use when starting a new project with a Figma design file. Do not use when the design system docs already exist or when there is no Figma file.
Mozurok/fhorja.dev/.claude/skills/frontend-architecture-review Skill
6★ repoReview a frontend architecture at scale and gate micro-frontend adoption BEFORE building. The first step is an adopt-or-don't-adopt decision (default: you probably do not need micro-frontends; prefer a modular monolith until 3 or more independently deploying teams and real coordination pain exist), then a checklist covering team-and-domain boundaries, independent deployability, governed shared dependencies, design-system sharing, runtime isolation, cross-app communication, routing and composition tier, rendering strategy, state at scale, a performance budget across the composition, and governance and failure handling. Capability-routed, not stack-locked. Use when reviewing a frontend architecture, evaluating whether to adopt micro-frontends, or hardening a multi-team frontend before it scales. Do not use to design one system (use frontend-system-design), to review a GraphQL or REST contract (use graphql-contract-review or api-contract-review), or with no active task folder (run task-init first).
Mozurok/fhorja.dev/.claude/skills/frontend-system-design Skill
6★ repoProduce a staff-grade frontend system-design RFC for the active task: a 12-section design document (problem, requirements, architecture, data model, API and interface contract, rendering and delivery, state management, performance budget, accessibility, security, rollout, trade-offs) covering web and mobile, persisted as FRONTEND_SYSTEM_DESIGN.md. The default mode writes the design doc for real work; an --interview mode reframes the same structure for a frontend system-design interview round (RADIO-aligned). Capability-routed, not React-specific. Use when a frontend feature or surface needs an architecture-level design before planning and slicing, or when preparing a system-design interview artifact. Do not use to frame whether the problem is right (use problem-framing), to slice an already-designed change (use implementation-plan), to analyze blast radius (use impact-analysis), to review an API contract in isolation (use api-contract-review), or with no active task folder (run task-init first).
Mozurok/fhorja.dev/.claude/skills/graphql-contract-review Skill
6★ repoReview a GraphQL schema and a Backend-for-Frontend (BFF) contract BEFORE implementation, against a GraphQL-specific checklist: schema shape and nullability (null-bubbling), errors-as-data unions, N+1 and DataLoader, query cost and depth limits, cursor-connection pagination, federation entity ownership, breaking-change gate (schema checks), auth layering and BFF token posture, BFF thinness, and partial-failure degradation. Distinct from api-contract-review (REST and HTTP) and review-hard (post-implementation risk). Capability-routed, not stack-locked. Use when designing a new GraphQL schema, a federated subgraph, or a BFF contract, or modifying an existing one. Do not use for a REST contract (use api-contract-review), when the schema is already implemented (use review-hard or repo-consistency-sweep), or with no active task folder (run task-init first).
Mozurok/fhorja.dev/.claude/skills/impact-analysis Skill
6★ repoUnderstand the requested change deeply enough to make safe workflow decisions, then persist the analysis as IMPACT_ANALYSIS.md in the active task folder. Per-repo subsections when multi-repo. Identifies blast radius, contract impacts, schema/runtime risks, and integration points before planning or coding. Use when a new task was just initialized, the task is still unclear or partially understood, the blast radius is not yet known, or the request may affect contracts, schema, integrations, runtime behavior, or critical user flows. Do not use when the task is already in a well-defined planning phase with valid impact analysis, the goal is only to sync task memory after progress, the main issue is an observed technical failure (use incident-triage), or the current need is to implement an already-approved slice (use implement-approved-slice). For greenfield work, consider backend-system-design, frontend-architecture-review, ai-feature-eval-harness, or code-context-map.
Mozurok/fhorja.dev/.claude/skills/incident-triage Skill
6★ repoTriage a concrete observed technical failure (stack trace, error, failing test, runtime symptom, production alert), classify the failure type (REGRESSION/NEW_BUG/CONFIG/EXTERNAL_DEPENDENCY/REPRODUCIBILITY/DIAGNOSTIC_INSUFFICIENT), recommend fix size (HOTFIX/SLICE/INVESTIGATION/ESCALATE), and validate against locked decisions and invariants. Defends HOTFIX paths against unnecessary ceremony with explicit safety justification. Use when there is concrete failure evidence, an active task folder exists, urgency is real or unclear, or it is unclear whether to run the full flow or take a hotfix shortcut. Do not use when the issue is not concrete (use im-stuck or what-next), the failure is feature-shaped (use task-init for a new feature task), the fix is already implemented and only delivery remains (use pr-package), the failure surfaced from PR feedback (use pr-feedback-ingest or post-review-pivot), or no active task folder exists yet.
Mozurok/fhorja.dev/.claude/skills/project-bootstrap Skill
6★ repoInitialize a new project context inside the task repository before any task exists. Creates projects/<client>__<project>/, PROJECT_CHARTER.md, REFERENCES.md skeleton, and active/ plus archive/ subfolders so subsequent task-init runs have grounded project-level memory to consume. Use when starting a brand-new project, product, initiative, or client engagement, projects/<client>__<project>/ does not yet exist, or you need to capture project-level context (objective, stack, planned repositories, constraints, references) before opening the first task. Do not use when the project folder already exists (use task-init to start a new task on top of it), you only need a new task on an existing project, you only need to capture external references for an existing project (use capture-references), or the work is task-scoped and short enough that bootstrap ceremony adds no value.