Menu
Skills dans ce dépôt
SkillsMP a collecté 1 313 skills depuis jeffreytse/grimoire-core. Ouvrez un skill pour examiner sa source et ses détails.
jeffreytse/grimoire-coreAffichage de 40 skills collectés sur 1 313.
Use when writing Solidity contracts that need randomness — NFT mints, lotteries, games — replacing insecure block variable entropy with Chainlink VRF or commit-reveal to prevent miner manipulation.
Langue du texte source : anglais
Use when writing DeFi smart contracts that rely on price feeds, randomness, or external data — preventing oracle manipulation via TWAP, multiple oracle sources, and circuit breakers.
Langue du texte source : anglais
Use when writing DeFi smart contracts with user-submitted transactions — implementing commit-reveal, slippage tolerance, and MEV-resistant patterns to prevent front-running and sandwich attacks.
Langue du texte source : anglais
Use when writing Solidity smart contracts that transfer ETH or call external contracts — applying the Checks-Effects-Interactions pattern and ReentrancyGuard to prevent reentrancy attacks.
Langue du texte source : anglais
Use when auditing a Solidity smart contract or reviewing a protocol before deployment — systematically checking all 10 OWASP Smart Contract Top 10 vulnerability classes with Slither/Foundry test procedures.
Langue du texte source : anglais
Use when running workloads in cloud environments — enabling GuardDuty, Security Command Center, or Microsoft Defender, and deploying Falco for Kubernetes runtime threat detection.
Langue du texte source : anglais
Use when writing serverless functions (AWS Lambda, Google Cloud Functions, Azure Functions) — validating event data from all trigger sources, preventing execution flow manipulation, and securing error handling.
Langue du texte source : anglais
Use when writing serverless functions — assigning per-function IAM execution roles with minimal permissions, disabling unused triggers, and securing function URLs and API authentication.
Langue du texte source : anglais
Use when managing secrets in serverless functions — replacing environment variable credentials with Secrets Manager or Parameter Store, auditing third-party Lambda layers, and preventing secret leakage in logs.
Langue du texte source : anglais
Use when building or refactoring cloud-native applications to ensure portability, scalability, and operability across environments
Langue du texte source : anglais
Use when estimating, forecasting, or auditing cloud infrastructure costs before provisioning, during architecture review, or at budget planning time
Langue du texte source : anglais
Use when designing cloud network architecture — structuring VPCs with public/private subnets, using VPC endpoints for AWS service access, and implementing security groups as stateful firewalls to contain blast radius.
Langue du texte source : anglais
Use when Kubernetes pods or cloud services need to access cloud APIs — replacing long-lived IAM keys with IRSA (AWS), Workload Identity (GCP), or Managed Identity (Azure) to eliminate credential leakage risks.
Langue du texte source : anglais
Use when establishing or auditing business continuity for cloud systems that must recover from catastrophic failures, data loss, or prolonged outages
Langue du texte source : anglais
Use when designing systems that must survive regional outages, minimize global latency, or meet geographic data residency requirements
Langue du texte source : anglais
Use when deploying serverless functions at scale — setting reserved concurrency, SQS visibility timeouts, recursion detection, and budget alerts to prevent denial-of-service via financial resource exhaustion.
Langue du texte source : anglais
Use when operating serverless functions in production — implementing structured logging, distributed tracing, anomaly-based alerting, and cold start monitoring to detect security incidents and performance degradation.
Langue du texte source : anglais
Use when cloud costs are growing faster than usage, when preparing for budget reviews, or when seeking to reduce infrastructure spend without degrading performance
Langue du texte source : anglais
Use when auditing a cloud-native application or infrastructure — systematically checking all 10 OWASP Cloud-Native Application Security Top 10 vulnerability classes with AWS CLI, kubectl, and Terraform commands.
Langue du texte source : anglais
Use when designing a data governance policy covering data ownership, classification, access control, lifecycle management, and regulatory compliance
Langue du texte source : anglais
Use when designing a new relational database schema, adding entities to an existing system, reviewing a schema for normalization issues, or planning migrations — before writing DDL or ORM models.
Langue du texte source : anglais
Use when designing, building, or reviewing a data pipeline for ingestion, transformation, or analytics
Langue du texte source : anglais
Use when designing a systematic data quality framework covering completeness, accuracy, consistency, timeliness, validity, and uniqueness across data pipelines and data warehouses
Langue du texte source : anglais
Use when writing, reviewing, or optimizing SQL queries for correctness, performance, and maintainability
Langue du texte source : anglais
Use when replacing a large or deeply integrated component of a system incrementally without creating a long-lived feature branch, by introducing an abstraction layer that allows old and new implementations to coexist.
Langue du texte source : anglais
Use when a monorepo contains multiple independently versioned packages and each package needs its own changelog updated only when that package has actual changes.
Langue du texte source : anglais
Use when designing a project structure, framework, or tooling setup and deciding how much explicit configuration to require from developers.
Langue du texte source : anglais
Use when writing constructors, setters, or methods that accept or return mutable objects — to prevent callers from silently mutating internal state through shared object references.
Langue du texte source : anglais
Use when you notice duplicated code, logic, data, or knowledge across a codebase and need to decide whether and how to consolidate it.
Langue du texte source : anglais
Use when writing functions, modules, or services to assert internal assumptions — preconditions, postconditions, invariants — so that violated assumptions produce an immediate, loud error at the point of violation rather than propagating corrupt state…
Langue du texte source : anglais
Use when contributing to a repository you cannot push to directly — to fork the repo, develop on your fork, keep it in sync with upstream, and submit changes via pull request without requiring write access to the canonical repository.
Langue du texte source : anglais
Use when a team has scheduled releases, maintains multiple supported versions simultaneously, or operates in a regulated environment requiring formal release approval gates.
Langue du texte source : anglais
Use when a team deploys continuously from a single mainline — to keep `main` always deployable, use short-lived feature branches, and ship via PR without release branches or long-lived parallel branches.
Langue du texte source : anglais
Use when deploying to multiple environments (staging, pre-production, production) and needing a branch-per-environment promotion model that is simpler than GitFlow but more structured than GitHub Flow.
Langue du texte source : anglais
Use when writing or reviewing code in a specific language or ecosystem — especially when contributors from different language backgrounds write in conflicting styles, or when code compiles but feels foreign to native speakers of the language.
Langue du texte source : anglais
Use when reviewing or writing code that feels unnecessarily complex, clever, or hard to follow — to simplify implementation without losing correctness.
Langue du texte source : anglais
Use when onboarding new engineers, tackling high-complexity problems, debugging subtle issues, or when code quality and knowledge sharing are priorities over individual throughput
Langue du texte source : anglais
Use when evolving a public API, shared interface, or data schema in a way that must remain backward-compatible with existing consumers during the migration period.
Langue du texte source : anglais
Use when writing or reviewing functions and modules — especially when callers encounter surprising side effects, error handling is inconsistent, or debugging requires tracing hidden state changes.
Langue du texte source : anglais
Use when deciding how to handle a change in a code review workflow — to categorize each change as Ship (merge without review), Show (merge then notify), or Ask (open for discussion before merging), reducing review bottlenecks without eliminating oversight.
Langue du texte source : anglais