$npx -y skills add DNYoussef/context-cascade --skill sop-api-development/*============================================================================*/ /* SOP-API-DEVELOPMENT SKILL :: VERILINGUA x VERIX EDITION */ /*============================================================================*/
| 1 | /*============================================================================*/ |
| 2 | /* SOP-API-DEVELOPMENT SKILL :: VERILINGUA x VERIX EDITION */ |
| 3 | /*============================================================================*/ |
| 4 | |
| 5 | --- |
| 6 | name: sop-api-development |
| 7 | version: 1.0.0 |
| 8 | description: | |
| 9 | [assert|neutral] Complete REST API development workflow coordinating backend, database, testing, documentation, and DevOps agents. 2-week timeline with TDD approach. [ground:given] [conf:0.95] [state:confirmed] |
| 10 | category: delivery |
| 11 | tags: |
| 12 | - delivery |
| 13 | - development |
| 14 | - workflow |
| 15 | author: ruv |
| 16 | cognitive_frame: |
| 17 | primary: evidential |
| 18 | goal_analysis: |
| 19 | first_order: "Execute sop-api-development workflow" |
| 20 | second_order: "Ensure quality and consistency" |
| 21 | third_order: "Enable systematic delivery processes" |
| 22 | --- |
| 23 | |
| 24 | /*----------------------------------------------------------------------------*/ |
| 25 | /* S0 META-IDENTITY */ |
| 26 | /*----------------------------------------------------------------------------*/ |
| 27 | |
| 28 | [define|neutral] SKILL := { |
| 29 | name: "sop-api-development", |
| 30 | category: "delivery", |
| 31 | version: "1.0.0", |
| 32 | layer: L1 |
| 33 | } [ground:given] [conf:1.0] [state:confirmed] |
| 34 | |
| 35 | /*----------------------------------------------------------------------------*/ |
| 36 | /* S1 COGNITIVE FRAME */ |
| 37 | /*----------------------------------------------------------------------------*/ |
| 38 | |
| 39 | [define|neutral] COGNITIVE_FRAME := { |
| 40 | frame: "Evidential", |
| 41 | source: "Turkish", |
| 42 | force: "How do you know?" |
| 43 | } [ground:cognitive-science] [conf:0.92] [state:confirmed] |
| 44 | |
| 45 | ## Kanitsal Cerceve (Evidential Frame Activation) |
| 46 | Kaynak dogrulama modu etkin. |
| 47 | |
| 48 | /*----------------------------------------------------------------------------*/ |
| 49 | /* S2 TRIGGER CONDITIONS */ |
| 50 | /*----------------------------------------------------------------------------*/ |
| 51 | |
| 52 | [define|neutral] TRIGGER_POSITIVE := { |
| 53 | keywords: ["sop-api-development", "delivery", "workflow"], |
| 54 | context: "user needs sop-api-development capability" |
| 55 | } [ground:given] [conf:1.0] [state:confirmed] |
| 56 | |
| 57 | /*----------------------------------------------------------------------------*/ |
| 58 | /* S3 CORE CONTENT */ |
| 59 | /*----------------------------------------------------------------------------*/ |
| 60 | |
| 61 | # SOP: REST API Development |
| 62 | |
| 63 | ## Kanitsal Cerceve (Evidential Frame Activation) |
| 64 | Kaynak dogrulama modu etkin. |
| 65 | |
| 66 | |
| 67 | |
| 68 | |
| 69 | ## When to Use This Skill |
| 70 | |
| 71 | - **Domain-Specific Work**: Tasks requiring specialized domain knowledge |
| 72 | - **Complex Problems**: Multi-faceted challenges needing systematic approach |
| 73 | - **Best Practice Implementation**: Following industry-standard methodologies |
| 74 | - **Quality-Critical Work**: Production code requiring high standards |
| 75 | - **Team Collaboration**: Coordinated work following shared processes |
| 76 | |
| 77 | ## When NOT to Use This Skill |
| 78 | |
| 79 | - **Outside Domain**: Tasks outside this skill specialty area |
| 80 | - **Incompatible Tech Stack**: Technologies not covered by this skill |
| 81 | - **Simple Tasks**: Trivial work not requiring specialized knowledge |
| 82 | - **Exploratory Work**: Experimental code without production requirements |
| 83 | |
| 84 | ## Success Criteria |
| 85 | |
| 86 | - [ ] Implementation complete and functional |
| 87 | - [ ] Tests passing with adequate coverage |
| 88 | - [ ] Code reviewed and approved |
| 89 | - [ ] Documentation updated |
| 90 | - [ ] Performance benchmarks met |
| 91 | - [ ] Security considerations addressed |
| 92 | - [ ] Deployed or integrated successfully |
| 93 | |
| 94 | ## Edge Cases to Handle |
| 95 | |
| 96 | - **Legacy Integration**: Working with older codebases or deprecated APIs |
| 97 | - **Missing Dependencies**: Unavailable libraries or external services |
| 98 | - **Version Conflicts**: Dependency version incompatibilities |
| 99 | - **Data Issues**: Malformed input or edge case data |
| 100 | - **Concurrency**: Race conditions or synchronization challenges |
| 101 | - **Error Handling**: Graceful degradation and recovery |
| 102 | |
| 103 | ## Guardrails |
| 104 | |
| 105 | - **NEVER** skip testing to ship faster |
| 106 | - **ALWAYS** follow domain-specific best practices |
| 107 | - **NEVER** commit untested or broken code |
| 108 | - **ALWAYS** document complex logic and decisions |
| 109 | - **NEVER** hardcode sensitive data or credentials |
| 110 | - **ALWAYS** validate input and handle errors gracefully |
| 111 | - **NEVER** deploy without reviewing changes |
| 112 | |
| 113 | ## Evidence-Based Validation |
| 114 | |
| 115 | - [ ] Automated tests passing |
| 116 | - [ ] Code linter/formatter passing |
| 117 | - [ ] Security scan completed |
| 118 | - [ ] Performance within acceptable range |
| 119 | - [ ] Manual testing completed |
| 120 | - [ ] Peer review approved |
| 121 | - [ ] Documentation reviewed |
| 122 | |
| 123 | Complete REST API development using Test-Driven Development and multi-agent coordination. |
| 124 | |
| 125 | ## Timeline: 2 Weeks |
| 126 | |
| 127 | **Phases**: |
| 128 | 1. Planning & Design (Days 1-2) |
| 129 | 2. Development (Days 3-8) |
| 130 | 3. Testing & Documentation (Days 9-11) |
| 131 | 4. Deployment (Days 12-14) |
| 132 | |
| 133 | --- |
| 134 | |
| 135 | ## Phase 1: Planning & Design (Days 1-2) |
| 136 | |
| 137 | ### Day 1: Requirements & Architecture |
| 138 | |
| 139 | **Sequential Workflow**: |
| 140 | |
| 141 | ```javascript |
| 142 | // Step 1: Gather Requirements |
| 143 | await Task("Product Manager", ` |
| 144 | Define API requirements: |
| 145 | - List a |