← all publishers

LeadcodeDev

@leadcodedev source repo

Report this profile Claim this profile

• 3 skills
• 0 followers
• 8 hours ago last updated

1. ▌
   Audit · leadcodedev bundle

   Use when auditing, reviewing, hardening, or assessing code — a whole codebase, a single module, a branch diff, staged changes, or a PR. Triggers include 'audit', 'code review', 'security review', 'find vulnerabilities', 'check for weaknesses', 'is this code safe', 'pre-release review', 'what could go wrong here', 'quality review', 'this is getting messy', 'improve the architecture', 'find refactoring opportunities', 'is this abstraction worth it'. Any language, any layer: backend, frontend, CLI, library, infrastructure-as-code. Defensive purpose only: findings and remediation, never exploit development.
   0
   installs
2. ▌
   Dev Methodology · leadcodedev bundle

   Engineering methodology and behavioral guardrails for building applications. Consult this skill whenever writing, modifying, reviewing, debugging, architecting, testing, or deploying code — including new features, bug fixes, refactors, infrastructure changes, CI/CD work, and design discussions. Also consult it when decomposing a feature into workstreams (chantiers), dispatching sub-agents, or coordinating parallel implementation — it defines how sub-agents are briefed, partitioned, and verified. Apply it even when the user doesn't ask for "methodology" or "best practices" — it governs how development work is done, not just what is delivered. Consult it too when deciding whether to act or ask, when a message reads as either question or instruction, or when judging whether work is finished. Especially relevant for Rust projects, hexagonal/port-adapter architectures, and open-source codebases, but the core rules apply to any language or stack.
   0
   installs
3. ▌
   Writing Article · leadcodedev bundle

   Explainer Article Writer
   0
   installs