jeffreytse/grimoire-core - 25ページ

apply-trunk-based-development

Use when teams want to increase deployment frequency, reduce merge conflicts, or adopt continuous integration and delivery practices

原文の言語: 英語

apply-yagni-principle

Use when deciding whether to add a feature, abstraction, configuration option, or generalization that isn't required by a current, concrete requirement.

原文の言語: 英語

bisect-regression

Use when a test or behavior that previously worked is now broken and the commit that introduced the regression is unknown — to use `git bisect` to binary-search the commit history and identify the exact commit that caused it.

原文の言語: 英語

design-branching-strategy

Use when choosing or designing a Git branching model for a team or project

原文の言語: 英語

design-code-review-process

Use when establishing or improving a team's code review workflow, when reviews are causing bottlenecks, or when quality issues are escaping review into production

原文の言語: 英語

design-grpc-service

Use when building a gRPC service — to define the proto contract first, apply field numbering and naming conventions, model errors with google.rpc.Status, handle streaming patterns, and maintain backward compatibility across versions.

原文の言語: 英語

design-naming-convention

Use when establishing naming conventions for a new artifact type — APIs, database tables, files, functions, CLI commands, event names, skill libraries, or any identifier namespace that multiple contributors will add to over time.

原文の言語: 英語

design-restful-api

Use when designing HTTP API endpoints — choosing resource names, HTTP methods, status codes, versioning strategy, and response shapes.

原文の言語: 英語

diagnose-bug

Use when a bug, test failure, crash, or unexpected behavior is reported — before proposing any fix. Use when behavior diverges from specification and the root cause is unknown.

原文の言語: 英語

propose-conventional-commit

Use when the user asks to commit or wants a git commit message drafted — for any staged changes, whether or not they know the Conventional Commits format.

原文の言語: 英語

review-code-style

Use when reviewing code for style consistency, readability, or adherence to a team or language style guide

原文の言語: 英語

review-pull-request

Use when asked to review a pull request, diff, or code change — whether reviewing as an AI assistant or guiding a human reviewer on what to check and how to give feedback.

原文の言語: 英語

run-changelog-automation

Use when a software project enforces Conventional Commits and wants automated changelog generation and semantic version bumping without manual writing at each release.

原文の言語: 英語

triage-bug-report

Use when a bug report is filed — to reproduce it, assess severity and priority, capture required context, and assign it before any diagnosis begins.

原文の言語: 英語

write-changelog

Use when writing or updating a CHANGELOG for a software project before a release

原文の言語: 英語

write-database-migration

Use when changing a database schema — adding or removing columns, creating tables, adding indexes, or altering constraints.

原文の言語: 英語

write-openapi-spec

Use when writing or reviewing an OpenAPI 3.x specification — to apply naming conventions, schema reuse, error modeling, pagination, security schemes, and examples that make the spec complete, consistent, and usable as a contract.

原文の言語: 英語

write-review-comments

Use when writing code review comments — to phrase feedback in a way that is kind, clear, and actionable; distinguishes blocking from optional suggestions; and helps the author improve without feeling attacked.

原文の言語: 英語

apply-docker-security

Use when writing Dockerfiles, configuring container runtimes, or deploying containerized workloads — to harden containers against privilege escalation, image vulnerabilities, and container escape.

原文の言語: 英語

apply-feature-toggles

Use when you need to separate code deployment from feature release, enable A/B testing, implement gradual rollouts, or allow rapid disabling of features in production without a rollback deployment.

原文の言語: 英語

apply-iac-security

Use when writing Terraform, CloudFormation, Pulumi, or Bicep templates — to detect misconfigurations, enforce least privilege IAM, and prevent insecure defaults before infrastructure reaches production.

原文の言語: 英語

apply-kubernetes-security

Use when deploying workloads to Kubernetes — configuring RBAC, network policies, pod security standards, secrets management, and admission controls to prevent privilege escalation and lateral movement.

原文の言語: 英語

design-cicd-pipeline-security

Use when designing or hardening CI/CD pipelines — securing secret injection, restricting pipeline permissions, signing artifacts, and preventing supply chain attacks in GitHub Actions, GitLab CI, or Jenkins.

原文の言語: 英語

design-deployment-strategy

Use when selecting or designing a deployment strategy for releasing software to production safely

原文の言語: 英語

design-gitops-workflow

Use when designing a GitOps workflow where Git is the single source of truth for infrastructure and application configuration, with automated reconciliation to the desired state

原文の言語: 英語

design-platform-engineering-model

Use when designing an internal developer platform (IDP) to reduce cognitive load on product teams, standardize infrastructure access, and improve developer experience at scale

原文の言語: 英語

plan-incident-response

Use when a production incident is declared or suspected, when building an incident response runbook, or when running a post-incident review that needs a structured process.

原文の言語: 英語

write-post-mortem

Use when an incident, outage, or significant production failure has occurred and needs to be documented — including partial outages, data pipeline failures, degraded performance events, or security incidents. Trigger once the incident is resolved and…

原文の言語: 英語

design-contribution-standard

Use when creating quality standards for a knowledge repository, skill library, documentation site, or any artifact collection that will accept external contributors over time — including when the current standard has grown inconsistent or unenforced.

原文の言語: 英語

design-component-api

Use when designing the props interface, composition model, or public API for a reusable React or UI component

原文の言語: 英語

design-component

Use when creating a new UI component, refactoring an existing one into something reusable, or reviewing a component design for composability, accessibility, and maintainability before implementation.

原文の言語: 英語

apply-iot-device-hardening

Use when preparing IoT devices for production deployment — removing default credentials, disabling debug interfaces, encrypting stored data, and implementing physical tamper detection.

原文の言語: 英語

apply-iot-network-hardening

Use when designing IoT device network interfaces — disabling unnecessary services, enforcing TLS for all communication, segmenting devices on isolated VLANs, and securing management APIs.

原文の言語: 英語

design-iot-device-management

Use when building IoT fleet management infrastructure — designing secure device provisioning, certificate lifecycle, remote management, and decommissioning processes.

原文の言語: 英語

design-iot-secure-boot

Use when designing firmware update mechanisms for IoT devices — implementing code signing, secure boot chains, and rollback protection to prevent malicious firmware from running on deployed hardware.

原文の言語: 英語

review-iot-security

Use when auditing an IoT product or deployment — systematically checking all 10 OWASP IoT Top 10 vulnerability classes with test procedures, firmware analysis commands, and network scanning.

原文の言語: 英語

apply-mobile-code-hardening

Use when preparing a mobile app for production release — especially apps handling financial data, DRM content, or anti-cheat systems — to raise the bar against reverse engineering, tampering, and runtime manipulation.

原文の言語: 英語

apply-mobile-cryptography

Use when implementing cryptographic operations in a mobile app — encrypting data, hashing passwords, generating keys, signing data, or establishing secure communication channels between the app and backend.

原文の言語: 英語

apply-secure-mobile-storage

Use when storing sensitive data on a mobile device — credentials, tokens, PII, health data, financial data, or any data that should not be accessible to other apps or readable from device backups.

原文の言語: 英語

audit-mobile-performance

Use when diagnosing performance problems in a mobile app or conducting a systematic mobile performance review

原文の言語: 英語