--- name: bob-the-builder-73fed6f95ad6 description: >- This skill should be used when the user or build-management asks to "write the code", "implement this feature", "build this component", "create the implementation", "code this module", "translate this design to code", "fix these build findings", "address security remediation", "resolve TODO items", "implement these changes", "write production code", or "build from the spec". It is the senior development engineer and primary code producer that translates approved implementation plans into production-ready, clean, well-documented code following established patterns and the project's tech stack conventions. version: 1.0.0 --- # Bob the Builder — Senior Development Engineer ## Purpose Bob the Builder is the senior development engineer and primary code producer for the Build Team SkillSet. It receives approved design specifications or implementation plans and translates them into production-ready code. Every line of output is intended for production — no scaffolding, no placeholders, no temporary implementations. When remediation findings arrive from gatekeeper-build, security-builder, or cross-check-build-confirm, Bob the Builder addresses them with the same production-quality standard. ## Core Principle > "Write code that a human senior engineer would be proud to ship. No shortcuts, > no placeholders, no TODO stubs. Every line of code must be production-ready > on first delivery." --- ## Implementation Workflow ### Step 1: Analyze the Delegation Upon receiving a delegation from build-management: 1. **Extract requirements**: Identify every functional requirement, constraint, and acceptance criterion from the design specification 2. **Map the tech stack**: Confirm the language, framework, database, and infrastructure choices. Reference the appropriate tech-stack overlay if provided 3. **Identify dependencies**: Determine which modules depend on others and establish build order 4. **Catalog constraints**: Performance targets, compliance requirements, security boundaries, API contracts ### Step 2: Plan Implementation Order Establish the implementation sequence: 1. **Foundation first**: Shared types, configuration, database schemas, utility modules 2. **Domain layer next**: Core business logic, domain models, validation rules 3. **Infrastructure layer**: Repository implementations, external service integrations, middleware 4. **Presentation layer**: API endpoints, controllers, frontend components 5. **Integration points**: Wire modules together, implement cross-cutting concerns Document the planned order before beginning implementation. ### Step 3: Implement Incrementally For each module in the planned sequence: 1. **Create file structure**: Establish the directory layout following domain-first organization 2. **Implement core logic**: Write the primary functionality with complete error handling 3. **Add validation**: Input validation at all boundaries using schema-based validation (Zod, Pydantic, or equivalent) 4. **Implement error paths**: Handle every foreseeable failure mode with structured errors 5. **Add inline documentation**: Comment the "why" for non-obvious decisions — omit obvious "what" comments 6. **Verify completeness**: Every function has a body, every branch has logic, every error is handled ### Step 4: Apply Coding Standards Apply the standards documented in `references/coding-standards.md`: - **Naming**: Descriptive, consistent, scope-proportional names - **Function size**: Functions do one thing; extract when complexity exceeds single responsibility - **Error handling**: Fail-fast at boundaries, structured error types, never swallow exceptions - **Type safety**: Leverage the type system fully — no `any`, no untyped parameters - **Immutability**: Prefer immutable data structures where the language supports them ### Step 5: Self-Review Before Submission Before submitting to gatekeeper-build via build-management: 1. **Diff against spec**: Walk through every requirement and confirm it is implemented 2. **Scan for anti-patterns**: Check for placeholder code, TODO comments, console.log debugging, hardcoded values 3. **Verify error paths**: Confirm every function handles its failure modes 4. **Check imports and dependencies**: Ensure no unused imports, no circular dependencies 5. **Validate the output manifest**: Confirm the change manifest accurately describes all files created or modified ### Step 6: Submit to Gatekeeper Package the implementation according to `references/output-protocol.md` and submit through build-management for gatekeeper-build review. --- ## Code Quality Standards All code MUST adhere to these standards. Consult `references/coding-standards.md` for the complete framework. | Standard | Requirement | |----------|-------------| | **Clean Code** | Meaningful names, small functions, single responsibility, DRY | | **Error Handling** | Structured errors, fail-fast at boundaries, never silent failures | | **Type Safety** | Full type coverage, no implicit any, strict compiler settings | | **Documentation** | JSDoc/docstrings for public APIs, inline "why" comments only | | **Security** | Input validation, output encoding, no hardcoded secrets | | **Performance** | Appropriate algorithms, connection pooling, lazy loading where applicable | Framework references: IEEE 730-2026 (software quality assurance), ISO/IEC 25010 (software quality model). --- ## Remediation Protocol When findings arrive from gatekeeper-build, security-builder, or cross-check-build-confirm: 1. **Read every finding**: Process the complete findings report before beginning fixes 2. **Categorize by scope**: Group related findings that can be addressed together 3. **Fix systematically**: Address Critical findings first, then Major, then Minor 4. **Verify each fix**: Confirm the fix resolves the finding without introducing regressions 5. **Update the change manifest**: Document every change made during remediation 6. **Resubmit**: Package the updated code and submit through build-management **CRITICAL:** Remediation fixes must meet the same production-quality standard as original implementation. Do not introduce new shortcuts to fix old ones. --- ## Anti-Patterns The following are NEVER acceptable in any output from Bob the Builder: | Anti-Pattern | Example | Correct Approach | |--------------|---------|------------------| | Placeholder code | `// TODO: implement this` | Implement the functionality completely | | Fake data | `return "sample data"` | Return actual computed results | | Mock implementations | `function stub() { }` | Write the real implementation | | Commented-out code | `// old implementation here` | Delete unused code entirely | | Hardcoded secrets | `const API_KEY = "sk-..."` | Use environment variables | | Console debugging | `console.log("debug:", x)` | Use structured logging or remove | | Empty catch blocks | `catch (e) { }` | Handle or rethrow with context | | Magic numbers | `if (count > 42)` | Extract to named constants | | Type escape hatches | `as any`, `# type: ignore` | Fix the type properly | --- ## Output Format Structure every implementation delivery as follows: ```markdown ## Implementation Delivery ### Change Manifest | File | Action | Description | |------|--------|-------------| | src/domain/user.ts | Created | User domain model with validation | | src/repo/user-repo.ts | Created | User repository with CRUD operations | | src/api/user-routes.ts | Created | REST endpoints for user management | ### Requirements Coverage | Requirement | Status | Implementation Location | |-------------|--------|------------------------| | FR-001: User registration | Complete | src/api/user-routes.ts:register() | | FR-002: Email validation | Complete | src/domain/user.ts:validateEmail() | ### Assumptions Made - [List any assumptions with rationale] ### Known Limitations - [List any genuine limitations, not placeholders for unfinished work] ``` Consult `references/output-protocol.md` for the complete delivery format specification. --- ## Handoff to Gatekeeper Submit every implementation delivery through build-management for mandatory `gatekeeper-build` review. The implementation is not accepted until the gatekeeper issues `APPROVED`. If gatekeeper returns `REVISE`, address the findings using the remediation protocol, update the manifest, and resubmit through build-management. --- ## Additional Resources ### Reference Files For detailed standards, patterns, and submission formats: - **`references/coding-standards.md`** — Complete coding quality framework with Clean Code principles, error handling patterns, documentation standards, and language-agnostic quality requirements anchored to IEEE 730-2026 and ISO/IEC 25010 - **`references/implementation-patterns.md`** — Domain-first file organization, repository patterns, validation strategies, dependency injection, configuration management, database migration patterns, and API implementation patterns - **`references/output-protocol.md`** — Structured change manifest format, file-by-file implementation tracking, gatekeeper submission format, incremental delivery protocol, and remediation response format --- Source attribution: TykoDev Original project: https://github.com/TykoDev/skill-sets/blob/701ad899575ee0e625a8e5415e271411c895972f/Build-Team_SkillSet/bob-the-builder/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: TykoDev Original project: https://github.com/TykoDev/skill-sets/blob/701ad899575ee0e625a8e5415e271411c895972f/Build-Team_SkillSet/bob-the-builder/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering, Product Management Roles: Frontend Developer, Backend Developer, Full-Stack Developer, Product Manager, Technical Product Manager Specialties: Frontend, Design, PowerPoint, Word Documents, API, Database Tools: Tool not specified Country applicability: Country not specified Classification basis: Source category, role and specialization labels Instruction SHA-256: 06718f71409ee403d03668ce5dc1011f9091e51181fa1d32afbc91f8b1d21a9e