Convert implementation plans into production-ready code with gettext i18n and multi-tenant scoping.
npx skills add https://github.com/ruimfernandes/claude --skill bob-builder
Please help me install this Agent Skill. Skill: bob-builder Source: https://github.com/ruimfernandes/claude/tree/main/skills/bob-builder Command: npx skills add https://github.com/ruimfernandes/claude --skill bob-builder
It turns an implementation plan into reliable, readable code without drifting into guesswork or scope creep, so delivered features match the spec and stay maintainable.
Apply the skill when you want to execute this implementation plan step by step and produce final production-ready code (including any needed tests) that follows the plan exactly.
High-intent search queries and answers about installing and using this skill.
Spec-driven coding converts an implementation plan into production-ready code by reading the full plan, restating it briefly, and implementing only what the plan requires to prevent scope creep. This approach ensures delivered features match the spec while maintaining readability.
Enforcing multi-tenant isolation when building features from a spec requires applying scoped multi-tenant reads and writes during implementation. This ensures data isolation is handled directly within the generated production code.
Keeping pull request size within line budgets requires PR-size-aware commit slicing during implementation. This practice keeps changes within preferred limits of 800 lines and a hard max of 1000 lines, proposing splits when needed to maintain review discipline.
Spec-driven coding supports gettext-based i18n for user-facing strings. When implementing an execution plan, it enforces gettext-based internationalization constraints to ensure the production-ready output handles multiple languages correctly.
Implementing SonaUI compliant components from a multi-step requirement set involves executing the plan step by step while enforcing SonaUI compliance for all UI work. This guarantees generated interface code meets required architectural standards.
Automated plan execution should not be used when your implementation plan lacks detailed specifications or when feature development requires deviations from stated requirements. This approach strictly implements only what the plan dictates to minimize deviations.
orekyuuGuide code investigation, requirement elicitation, and specification document creation.
kevindreeReview code changes for correctness, readability, architecture, security, and performance.
buihuulocScan Unreal Engine C++ and Blueprint codebases for hardcoded strings and localization issues.
CallMeLuigiv2Enforce Rust naming, formatting, and lint conventions during code reviews.
