[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79YBFBXCC4RPRVJW232ESXM":3,"skill-same:01M79YBFBXCC4RPRVJW232ESXM":46},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M79YBFBXCC4RPRVJW232ESXM","fullstack-development",null,"brokenchapt3r\u002FAstralNexus","brokenchapt3r","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F95068437?v=4","01M79YABD4MATY2G2S7ZE7QBJ1","刘帅","01M79YABE8GY62H7QA05XEEMBT",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fbrokenchapt3r\u002FAstralNexus\u002Fblob\u002Fmain\u002Fsrc\u002FAstralNexus\u002Fskills\u002Ffullstack-development\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: fullstack-development\ndescription: 全栈开发 fullstack full-stack workflow: API contracts, database, frontend, live HTTP and browser checks, targeted repair and delivery evidence.\nplatforms: [windows, linux, macos]\n---\n\n# Fullstack Development\n\nUse the existing repository, dependency environment and task contract. This\nprocedure supplies execution order; it does not change acceptance requirements,\nfile ownership or the selected technology stack.\n\n## Establish a runnable vertical slice\n\n1. Read the entry point, dependency manifest, API\u002Fdata contract and existing\n   tests. Record the exact working directory, executable and startup\u002Ftest argv.\n   Do not repeatedly enumerate the whole project once these are known.\n2. Implement one user flow through database, API and UI. Reuse the agreed API\n   names and response shapes. Give producers explicit files and consumers\n   explicit dependencies. Parallelize independent features after this contract.\n3. Name the owner of the service process and test database. Start the service,\n   wait for its actual readiness response and record its address. A dead service\n   is an environment prerequisite to repair, not evidence that all business\n   assertions failed. Keep it available until dependent consumers finish.\n\n## Execute checks against the current implementation\n\nRun existing unit\u002Fintegration tests first. Exercise real HTTP and browser\nbehavior required by the task, including persistence after reload and relevant\npermission\u002Fbusiness boundaries. Record commands, exit codes, test case outcomes\nand tool receipts. A custom test adapter must summarize actual assertions in a\nformat specified by the runtime test execution contract. Never add a constant\nsuccess line or rewrite old failed receipts to satisfy the parser.\n\n## Repair one recorded gap\n\nUse `recovery_handoff.repair_procedures` when present. Carry the original\ncriterion and command forward. Inspect only the named failure and necessary\nimplementation paths first:\n\n- Missing summary: fix the test adapter\u002Fcollector, then rerun its assertions.\n- Missing execution: execute the required check after verifying prerequisites.\n- Failed assertion: repair the responsible implementation, then rerun.\n- Stale evidence: rerun on the current versions; do not refresh report dates.\n- Zero tests: repair test discovery\u002Fselection before reporting success.\n\nIf a prerequisite diagnosis is now false, provide the concrete contradictory\nevidence. If the fix belongs to another owner, return the file, required change\nand recheck command to the Governor. A report-only successor does not discharge\nthe test obligation. An implementation repair can be followed by a dependent\ntester carrying that same criterion.\n\n## Deliver after re-verification\n\nBind the final report to current test receipts and artifact versions. Preserve\nfailed history separately. Assemble and publish only after the required checks\npass. Report assembly, a completed node and a limited publication are not full\nacceptance. Do not start a new investigation or rewrite unaffected features\nmerely because a recovery node has a new identifier.\n","# Fullstack Development\n\nUse the existing repository, dependency environment and task contract. This\nprocedure supplies execution order; it does not change acceptance requirements,\nfile ownership or the selected technology stack.\n\n## Establish a runnable vertical slice\n\n1. Read the entry point, dependency manifest, API\u002Fdata contract and existing\n   tests. Record the exact working directory, executable and startup\u002Ftest argv.\n   Do not repeatedly enumerate the whole project once these are known.\n2. Implement one user flow through database, API and UI. Reuse the agreed API\n   names and response shapes. Give producers explicit files and consumers\n   explicit dependencies. Parallelize independent features after this contract.\n3. Name the owner of the service process and test database. Start the service,\n   wait for its actual readiness response and record its address. A dead service\n   is an environment prerequisite to repair, not evidence that all business\n   assertions failed. Keep it available until dependent consumers finish.\n\n## Execute checks against the current implementation\n\nRun existing unit\u002Fintegration tests first. Exercise real HTTP and browser\nbehavior required by the task, including persistence after reload and relevant\npermission\u002Fbusiness boundaries. Record commands, exit codes, test case outcomes\nand tool receipts. A custom test adapter must summarize actual assertions in a\nformat specified by the runtime test execution contract. Never add a constant\nsuccess line or rewrite old failed receipts to satisfy the parser.\n\n## Repair one recorded gap\n\nUse `recovery_handoff.repair_procedures` when present. Carry the original\ncriterion and command forward. Inspect only the named failure and necessary\nimplementation paths first:\n\n- Missing summary: fix the test adapter\u002Fcollector, then rerun its assertions.\n- Missing execution: execute the required check after verifying prerequisites.\n- Failed assertion: repair the responsible implementation, then rerun.\n- Stale evidence: rerun on the current versions; do not refresh report dates.\n- Zero tests: repair test discovery\u002Fselection before reporting success.\n\nIf a prerequisite diagnosis is now false, provide the concrete contradictory\nevidence. If the fix belongs to another owner, return the file, required change\nand recheck command to the Governor. A report-only successor does not discharge\nthe test obligation. An implementation repair can be followed by a dependent\ntester carrying that same criterion.\n\n## Deliver after re-verification\n\nBind the final report to current test receipts and artifact versions. Preserve\nfailed history separately. Assemble and publish only after the required checks\npass. Report assembly, a completed node and a limited publication are not full\nacceptance. Do not start a new investigation or rewrite unaffected features\nmerely because a recovery node has a new identifier.\n",{},"main","e991b69b0591f9558a348eab277cb246697ee3b8","src\u002FAstralNexus\u002Fskills\u002Ffullstack-development",0,"https:\u002F\u002Fgithub.com\u002Fbrokenchapt3r\u002FAstralNexus","https:\u002F\u002Fgithub.com\u002Fbrokenchapt3r","https:\u002F\u002Fwww.njupt.edu.cn\u002F","南京邮电大学","2026-10-12 12:27:42",{"source":7,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add brokenchapt3r\u002FAstralNexus --skill fullstack-development",{"tool":38,"command":39},"bunx","bunx skills add brokenchapt3r\u002FAstralNexus --skill fullstack-development",{"tool":41,"command":42},"pnpm","pnpm dlx skills add brokenchapt3r\u002FAstralNexus --skill fullstack-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbrokenchapt3r\u002FAstralNexus\u002Fblob\u002Fmain\u002Fsrc\u002FAstralNexus\u002Fskills\u002Ffullstack-development\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M79YCB4JGT3GSY8PGKVXFSA7","travel-device-coordination","Prepare multi-device business travel by organizing schedules, documents, sensitive data placement, connectivity, power, offline materials, and risks.","https:\u002F\u002Fgithub.com\u002Fbrokenchapt3r\u002FAstralNexus\u002Fblob\u002Fmain\u002Fsrc\u002FAstralNexus\u002Fskills\u002Ftravel-device-coordination\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M79YC6ERJG4C0HJ1RVQSJF94","supply-chain-planning","Build constrained supply, production, inventory, and logistics plans with scenarios, sensitivity analysis, and exception replanning.","https:\u002F\u002Fgithub.com\u002Fbrokenchapt3r\u002FAstralNexus\u002Fblob\u002Fmain\u002Fsrc\u002FAstralNexus\u002Fskills\u002Fsupply-chain-planning\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M79YC2NNXEFW8E8DWHVVFT1G","software-backend","Build and review production backend systems with explicit API, data, authorization, observability, testing, and deployment contracts.","https:\u002F\u002Fgithub.com\u002Fbrokenchapt3r\u002FAstralNexus\u002Fblob\u002Fmain\u002Fsrc\u002FAstralNexus\u002Fskills\u002Fsoftware-backend\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M79YBZZY6JXVZJPFSVH57PVC","scientific-research","Conduct evidence-backed literature analysis, hypothesis generation, baseline reproduction, minimal experiments, and falsifiable evaluation.","https:\u002F\u002Fgithub.com\u002Fbrokenchapt3r\u002FAstralNexus\u002Fblob\u002Fmain\u002Fsrc\u002FAstralNexus\u002Fskills\u002Fscientific-research\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M79YBVAYZ0W897E6RC2WFQM1","rag-retrieval","Design and evaluate production RAG pipelines with parsing, chunking, hybrid retrieval, reranking, citations, and multimodal context.","https:\u002F\u002Fgithub.com\u002Fbrokenchapt3r\u002FAstralNexus\u002Fblob\u002Fmain\u002Fsrc\u002FAstralNexus\u002Fskills\u002Frag-retrieval\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M79YBQTX47N3Y05DTJ3VGZTS","patent-analysis","Analyze prior art and draft patent materials with feature mapping, claim support, terminology consistency, and enablement checks.","https:\u002F\u002Fgithub.com\u002Fbrokenchapt3r\u002FAstralNexus\u002Fblob\u002Fmain\u002Fsrc\u002FAstralNexus\u002Fskills\u002Fpatent-analysis\u002FSKILL.md",[],[]]