jeffreytse/grimoire-core - 26페이지

design-mobile-privacy-controls

Use when building a mobile app that collects, processes, or transmits user data — implementing data minimization, purpose limitation, consent management, and user data controls required by app store policies and privacy regulations.

원문 언어: 영어

write-push-notification

Use when writing copy for push notifications or designing a push notification permission and delivery strategy

원문 언어: 영어

audit-network-security

Use when assessing network security posture before a production launch, after a security incident, during compliance assessment, or on a periodic security review cycle

원문 언어: 영어

design-network-segmentation

Use when designing network architecture for systems that handle sensitive data, require regulatory compliance, or need to contain blast radius from breaches

원문 언어: 영어

diagnose-network-latency

Use when users report slow response times, when SLO latency budgets are breached, or when investigating the network layer as a performance bottleneck

원문 언어: 영어

audit-bundle-size

Use when investigating JavaScript bundle size, slow Time to Interactive, or preparing a performance budget for a web application

원문 언어: 영어

audit-performance

Use when a system is slow, latency has regressed, CPU or memory usage is unexpectedly high, or before optimizing any code — to measure first, identify real bottlenecks, and prioritize fixes by impact.

원문 언어: 영어

calculate-capacity-plan

Use when provisioning infrastructure for a new system, preparing for anticipated traffic growth, or ensuring headroom before a major product launch

원문 언어: 영어

design-caching-strategy

Use when designing or auditing HTTP caching, CDN configuration, or application-level cache policies for a web service

원문 언어: 영어

diagnose-memory-leak

Use when a process shows continuously growing memory usage that doesn't stabilize, when OOM kills are occurring in production, or when heap dumps are needed to identify object accumulation

원문 언어: 영어

profile-web-vitals

Use when diagnosing web performance problems or preparing a performance audit for a website or web application

원문 언어: 영어

run-load-test

Use when validating system performance before a launch, during capacity planning, after significant code or infrastructure changes, or when investigating SLO latency budget breaches

원문 언어: 영어

design-experiment

Use when designing an A/B test or online controlled experiment to evaluate a product change

원문 언어: 영어

write-prd

Use when a new feature, product, or significant change needs to be defined before engineering begins — including greenfield features, major redesigns, API changes, or cross-team initiatives. Trigger when a problem or opportunity is validated and stakeholders…

원문 언어: 영어

write-release-note

Use when writing user-facing release notes for a software product release

원문 언어: 영어

write-user-story

Use when writing user stories, acceptance criteria, or backlog items for product features

원문 언어: 영어

plan-sprint

Use when starting a new sprint — to review the backlog, set the sprint goal, select stories, estimate capacity, and assign work before the team begins execution.

원문 언어: 영어

apply-five-whys

Use when investigating the root cause of a defect, incident, or recurring failure and need to move beyond symptoms to the underlying systemic cause.

원문 언어: 영어

audit-error-budget

Use when reviewing error budget consumption, setting burn rate alerts, or making reliability investment decisions based on budget status

원문 언어: 영어

design-slo

Use when defining or reviewing service reliability targets, error budgets, or SLI/SLO/SLA structures for a service

원문 언어: 영어

design-slo-sla-framework

Use when establishing reliability targets for services, defining error budgets for engineering teams, or negotiating service commitments with customers

원문 언어: 영어

run-game-day

Use when validating incident response capabilities, onboarding new engineers to on-call, preparing for a major launch, or after significant architecture changes

원문 언어: 영어

apply-api-client-security

Use when your application consumes external or third-party APIs — configuring HTTP clients, validating TLS certificates, handling secrets, and sanitizing responses from upstream services.

원문 언어: 영어

apply-api-rate-limiting

Use when building any API endpoint — especially authentication endpoints, resource-creation endpoints, and any operation with a per-user or per-tenant cost — to protect against abuse, brute force, and resource exhaustion.

원문 언어: 영어

apply-authorization-control

Use when implementing access control decisions — determining which users can perform which actions on which resources — in any API, web application, or service.

원문 언어: 영어

apply-content-security-policy

Use when deploying a web application that serves HTML — especially one with user-generated content, third-party scripts, or inline JavaScript — to restrict what resources the browser may load or execute.

원문 언어: 영어

apply-cors-policy

Use when building an API or web service that needs to be called from browser JavaScript on a different origin — including public APIs, microservices accessed from SPAs, and third-party integrations.

원문 언어: 영어

apply-cryptographic-storage

Use when storing sensitive data at rest — PII, health records, financial data, cryptographic keys, or any data that must remain confidential if storage media is compromised.

원문 언어: 영어

apply-graphql-security

Use when building or securing a GraphQL API — limiting query depth and complexity, disabling introspection in production, enforcing field-level authorization, and preventing batching abuse.

원문 언어: 영어

apply-jwt-security

Use when implementing JWT-based authentication or authorization — covering token generation, algorithm selection, validation, expiry, and revocation for stateless APIs.

원문 언어: 영어

apply-key-management

Use when designing encryption key lifecycle — generating, storing, rotating, and retiring cryptographic keys for application secrets, database encryption, and API signing keys.

원문 언어: 영어

apply-microservices-security

Use when building microservices that communicate with each other — implementing service-to-service mTLS, JWT propagation for user identity, and API gateway authentication to prevent lateral movement between services.

원문 언어: 영어

apply-password-hashing

Use when storing user passwords or credentials in a database — covers algorithm selection, work factor configuration, and migration from legacy hashing schemes.

원문 언어: 영어

apply-secure-defaults

Use when configuring a new application, framework, or service — ensuring security is enabled out of the box by setting restrictive defaults for cookies, headers, database connections, and framework security features.

원문 언어: 영어

apply-security-headers

Use when configuring any web server or application that serves HTTP responses to browsers — covers the full set of security response headers that harden against common attacks.

원문 언어: 영어

apply-tls-configuration

Use when configuring HTTPS on a web server, API gateway, or load balancer — covers cipher suites, TLS version enforcement, certificate management, and HSTS.

원문 언어: 영어

audit-cors-configuration

Use when you need to verify that a CORS policy is actually enforced correctly — after configuring CORS, before shipping an API, or during a security review. Tests origin reflection, null origin, subdomain bypass, wildcard-with-credentials, and preflight…

원문 언어: 영어

audit-dependency-vulnerabilities

Use when auditing third-party dependencies for known vulnerabilities, license issues, or supply chain risks

원문 언어: 영어

configure-cors-for-oauth

Use when building an OAuth 2.0 authorization server or configuring CORS on OAuth endpoints — token, userinfo, revocation, and introspection endpoints each have different CORS requirements that differ from ordinary API CORS.

원문 언어: 영어

design-auth-flow

Use when designing or reviewing authentication and authorization flows for web, mobile, or API systems

원문 언어: 영어