Explorez les skills IA publiés de claushaas et consultez leurs instructions source.
Skills indexés
26Étoiles des dépôts des skills indexés
16Forks du dépôt
0Moyenne des étoiles par skill indexé
1Les étoiles d’un dépôt peuvent se répéter entre ses skills.
Enforce the phase implementation workflow for Palette Kit v0.3 phases. Use when implementing a roadmap phase, creating a phase branch, validating the lint/typecheck/test/build pipeline, generating a patch for r...
Generate best-practice git commit messages (Conventional Commits) by inspecting changes, choosing type/scope, and producing concise, high-signal summaries in English.
Write or edit Markdown files while conforming to markdownlint rules used in this repo.
Implement APCA/WCAG2 contrast requirements and solver behavior per src/planning/spec-v0.3.md and src/planning/roadmap-v0.3.md, with minimal tests.
Review Palette Kit v0.3 changes using the official checklist and feedback template. Use when performing Copilot-assisted code reviews across phases 0-10 to verify contracts, DX, determinism, and phase-specific...
Audit public TypeScript types against src/planning/spec-v0.3.md, flag mismatches, and enforce acceptance criteria (build, no circular imports).
Implement or adjust the core color pipeline (parse, normalize, scale, resolve) guided by src/planning/spec-v0.3.md and src/planning/roadmap-v0.3.md.
Build CSS/JSON exporters per src/planning/spec-v0.3.md and src/planning/roadmap-v0.3.md, including output options and gamut handling.
Use this skill when you need expert guidance on React development with React Router V7, including component architecture, routing patterns, state management, performance optimization, and modern React best prac...
Plan and execute schema/data migrations safely with compatibility, backfills, and rollback. Use when changing data models, schemas, or storage.
Product analytics and feedback loop guidance for KPIs, funnels, and experimentation. Use when defining metrics instrumentation, experiments, or indicators of product success.
Define API contracts and typed boundaries between layers. Use when creating or modifying endpoints, schemas, or integrations.
Performance analysis and profiling focused on bottlenecks, latency, and resource usage. Use when there is slowness, high resource consumption, or unmet performance targets.
Add or improve observability (logs, metrics, traces, alerts) and troubleshoot production or performance issues. Use when diagnosing incidents, defining SLOs, or instrumenting critical paths.
Security review and pragmatic threat modeling for endpoints, authentication, sensitive data, and integrations. Use when there is user input, authentication, sensitive data handling, or payments.
Refactoring and safe modularization to reduce coupling, duplication, and complexity. Use when there is large code, cross-dependencies, or a need to extract modules.
Documentation and ADR updates for architectural decisions. Use when there are design changes, new features, or a need to record decisions.
Improve reliability via timeouts, retries, circuit breakers, degradation, and fault isolation. Use when failures, timeouts, or dependency flakiness impact users.
Plan system architecture and design for new features, large refactors, and long-term decisions; use when there is impact on components, data, integrations, or scalability.
Manage releases, deployments, and rollback strategy with clear versioning and environment policy. Use when planning or executing a release, or setting deployment workflow.
Define a testing strategy (unit, integration, end-to-end) based on repository risk and maturity. Use it when test coverage is lacking or when planning new features.
Triage build and CI failures with a focus on fixing errors quickly using minimal diffs. Use when the build fails locally or in CI.
Steward repository documentation as a living, versioned knowledge graph focused on consistency, continuity, traceability, and controlled evolution; use when documentation changes cross-cut multiple artifacts, c...
Code review focused on readability, maintainability, and clarity. Use after code changes, before merging, or when reviewing pull requests.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.