[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AA9P169A3Z88KDPTF8H2FX":3,"skill-same:01M7AA9P169A3Z88KDPTF8H2FX":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7AA9P169A3Z88KDPTF8H2FX","project-engineer",null,"Turn a design, idea, sketch, brief, or product concept into the simplest feasible project plan spanning design, deployment, security, operations, finance, tool reuse, and verification.","PolakiniO\u002FAI-Engineering-Playbook","PolakiniO","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F81532171?v=4","01M7AA8CXZRPFCA98M8HPNCNF7","Yuval Polak","01M7AA8CZ2W6P3T94B0YZREJQ6",2,"MIT","https:\u002F\u002Fgithub.com\u002FPolakiniO\u002FAI-Engineering-Playbook\u002Fblob\u002Fmain\u002Fskills\u002Fproject-engineer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: project-engineer\ndescription: Turn a design, idea, sketch, brief, or product concept into the simplest feasible project plan spanning design, deployment, security, operations, finance, tool reuse, and verification.\nmetadata:\n  short-description: Turn ideas into feasible project plans\n---\n\n# project-engineer\n\n## Purpose During Development\n\nUse this skill when Codex and similar AI coding agents need to turn a design, idea, sketch, brief, or product concept into a feasible project plan and implementation path.\n\nThis is a reusable development-time reasoning framework. It is not runtime code and must not be coupled into the product being built.\n\n## When To Apply\n\n- new project planning from an idea, design, prototype, screenshot, or vague brief\n- early implementation planning before repository structure, tooling, deployment, or cost model is clear\n- requests that need coordination across design, application engineering, deployment, security, operations, and finance engineering\n- project rescue work where the simplest feasible path needs to be recovered from an overbuilt plan\n\n## What To Inspect\n\n- the repository `AGENTS.md`, `PLAYBOOK.md`, and `skills\u002FPLAYBOOK.md`\n- existing source layout, package managers, CI, deployment files, infrastructure files, and environment examples\n- product brief, design inputs, screenshots, diagrams, tickets, or user-provided constraints\n- existing tools and services already present in the repo or organization\n- security, operations, and budget constraints that affect launch feasibility\n\n## Rules To Enforce\n\n- start with the smallest project shape that can satisfy the real user workflow\n- separate must-have launch scope from later polish, scale, and automation\n- reuse existing tools when they already fit the need and pass security review\n- avoid adding services, frameworks, queues, databases, or deployment layers before the project needs them\n- make deployment, security, operations, and cost decisions explicit before implementation hardens around them\n- keep design quality part of delivery, not a cosmetic final pass\n\n## Role Handoff Model\n\n- apply `product-designer` for user experience, visual direction, and non-generic design quality\n- apply `security-engineer` before adopting third-party tools, services, dependencies, or external integrations\n- apply `deployment-engineer` before choosing hosting, CI\u002FCD, environment strategy, or release flow\n- apply `operations-engineer` before defining observability, support, backup, incident, or runbook expectations\n- apply `finance-engineer` before committing to paid services, cloud resources, usage-based APIs, or scale assumptions\n- apply existing review skills from `skills\u002FPLAYBOOK.md` when implementation touches architecture, safety, contracts, performance, LLM behavior, or tests\n\n## Common Anti-Patterns To Catch\n\n- turning an idea into a platform before there is a validated workflow\n- choosing tools because they are fashionable rather than already present, simpler, safer, or cheaper\n- postponing deployment until after implementation creates awkward infrastructure requirements\n- treating security, operations, or cost as separate afterthoughts\n- accepting a generic AI-looking interface when the product needs a believable, domain-specific design\n\n## Expected Output From The Agent\n\n- project brief and success criteria\n- simplest feasible scope\n- role-by-role engineering plan\n- reuse-versus-build decisions\n- deployment path\n- security and operations guardrails\n- cost controls\n- implementation milestones\n- verification plan\n\n## Output Structure\n\n- Summary\n- Key Findings\n- Risks\n- Affected Files\n- Affected Areas\n- Simplest Feasible Path\n- Role Plan\n- Tool Reuse And Security Scan\n- Deployment Plan\n- Cost Controls\n- Suggested Improvements\n- Suggested Tests\n- Skills applied\n\n## Example Usage\n\n\"Use this skill to turn this app idea and screenshot into a buildable project with deployment, security, operations, and cost guidance.\"\n\n\"Plan the simplest feasible project from this design, reuse existing tools where safe, and give me a deployment path.\"\n","# project-engineer\n\n## Purpose During Development\n\nUse this skill when Codex and similar AI coding agents need to turn a design, idea, sketch, brief, or product concept into a feasible project plan and implementation path.\n\nThis is a reusable development-time reasoning framework. It is not runtime code and must not be coupled into the product being built.\n\n## When To Apply\n\n- new project planning from an idea, design, prototype, screenshot, or vague brief\n- early implementation planning before repository structure, tooling, deployment, or cost model is clear\n- requests that need coordination across design, application engineering, deployment, security, operations, and finance engineering\n- project rescue work where the simplest feasible path needs to be recovered from an overbuilt plan\n\n## What To Inspect\n\n- the repository `AGENTS.md`, `PLAYBOOK.md`, and `skills\u002FPLAYBOOK.md`\n- existing source layout, package managers, CI, deployment files, infrastructure files, and environment examples\n- product brief, design inputs, screenshots, diagrams, tickets, or user-provided constraints\n- existing tools and services already present in the repo or organization\n- security, operations, and budget constraints that affect launch feasibility\n\n## Rules To Enforce\n\n- start with the smallest project shape that can satisfy the real user workflow\n- separate must-have launch scope from later polish, scale, and automation\n- reuse existing tools when they already fit the need and pass security review\n- avoid adding services, frameworks, queues, databases, or deployment layers before the project needs them\n- make deployment, security, operations, and cost decisions explicit before implementation hardens around them\n- keep design quality part of delivery, not a cosmetic final pass\n\n## Role Handoff Model\n\n- apply `product-designer` for user experience, visual direction, and non-generic design quality\n- apply `security-engineer` before adopting third-party tools, services, dependencies, or external integrations\n- apply `deployment-engineer` before choosing hosting, CI\u002FCD, environment strategy, or release flow\n- apply `operations-engineer` before defining observability, support, backup, incident, or runbook expectations\n- apply `finance-engineer` before committing to paid services, cloud resources, usage-based APIs, or scale assumptions\n- apply existing review skills from `skills\u002FPLAYBOOK.md` when implementation touches architecture, safety, contracts, performance, LLM behavior, or tests\n\n## Common Anti-Patterns To Catch\n\n- turning an idea into a platform before there is a validated workflow\n- choosing tools because they are fashionable rather than already present, simpler, safer, or cheaper\n- postponing deployment until after implementation creates awkward infrastructure requirements\n- treating security, operations, or cost as separate afterthoughts\n- accepting a generic AI-looking interface when the product needs a believable, domain-specific design\n\n## Expected Output From The Agent\n\n- project brief and success criteria\n- simplest feasible scope\n- role-by-role engineering plan\n- reuse-versus-build decisions\n- deployment path\n- security and operations guardrails\n- cost controls\n- implementation milestones\n- verification plan\n\n## Output Structure\n\n- Summary\n- Key Findings\n- Risks\n- Affected Files\n- Affected Areas\n- Simplest Feasible Path\n- Role Plan\n- Tool Reuse And Security Scan\n- Deployment Plan\n- Cost Controls\n- Suggested Improvements\n- Suggested Tests\n- Skills applied\n\n## Example Usage\n\n\"Use this skill to turn this app idea and screenshot into a buildable project with deployment, security, operations, and cost guidance.\"\n\n\"Plan the simplest feasible project from this design, reuse existing tools where safe, and give me a deployment path.\"\n",{"name":5,"metadata":24,"description":7},{"short-description":25},"Turn ideas into feasible project plans","main","492387a8572f564f95c2dbe5e67f4b721595518c","skills\u002Fproject-engineer",1,"https:\u002F\u002Fgithub.com\u002FPolakiniO\u002FAI-Engineering-Playbook","https:\u002F\u002Fgithub.com\u002FPolakiniO","https:\u002F\u002Fpolakinio.com","🚀 Cybersecurity Engineer | DevOps Enthusiast\r\n🔐 DLP, SSE, threat mitigation\r\n💻 AI, Cloud, and Information Security ","2026-09-05 06:09:47",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add PolakiniO\u002FAI-Engineering-Playbook --skill project-engineer",{"tool":41,"command":42},"bunx","bunx skills add PolakiniO\u002FAI-Engineering-Playbook --skill project-engineer",{"tool":44,"command":45},"pnpm","pnpm dlx skills add PolakiniO\u002FAI-Engineering-Playbook --skill project-engineer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPolakiniO\u002FAI-Engineering-Playbook\u002Fblob\u002Fmain\u002Fskills\u002Fproject-engineer\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"README.md","REFERENCE","参考文档",653,"https:\u002F\u002Fgithub.com\u002FPolakiniO\u002FAI-Engineering-Playbook\u002Fblob\u002Fmain\u002Fskills\u002Fproject-engineer\u002FREADME.md",[56,63,70,77,84,91],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AAA2BNVXC31ESX02W6SQRE","test-strategy-reviewer","Assess verification scope, regression protection, and risk-based test coverage for changes under review or implementation.","https:\u002F\u002Fgithub.com\u002FPolakiniO\u002FAI-Engineering-Playbook\u002Fblob\u002Fmain\u002Fskills\u002Ftest-strategy-reviewer\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AA9XRKME6WEGEJJ6QCKX68","security-engineer","Plan or review project security, tool reuse, dependencies, services, integrations, permissions, secrets, supply-chain risk, and security scan requirements.","https:\u002F\u002Fgithub.com\u002FPolakiniO\u002FAI-Engineering-Playbook\u002Fblob\u002Fmain\u002Fskills\u002Fsecurity-engineer\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AA9SFJKV2YFE9Y4YANN9ZJ","scope-safety-guard","Review or plan changes that affect permissions, security boundaries, sensitive operations, external effects, or safety constraints.","https:\u002F\u002Fgithub.com\u002FPolakiniO\u002FAI-Engineering-Playbook\u002Fblob\u002Fmain\u002Fskills\u002Fscope-safety-guard\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AA9FZK6KHJ0GJTM7MDVGJZ","product-designer","Turn ideas, workflows, screenshots, or design briefs into credible product design direction and frontend guidance that avoids generic AI-looking UI.","https:\u002F\u002Fgithub.com\u002FPolakiniO\u002FAI-Engineering-Playbook\u002Fblob\u002Fmain\u002Fskills\u002Fproduct-designer\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AA9CYHSV3E5KFDXTPPAF2T","playbook-installer","Guide adoption of AI-Engineering-Playbook governance files in a portable, repeatable way across repositories.","https:\u002F\u002Fgithub.com\u002FPolakiniO\u002FAI-Engineering-Playbook\u002Fblob\u002Fmain\u002Fskills\u002Fplaybook-installer\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7AA9927ENV9ACB3ME4JMAWW","performance-optimizer","Review or plan changes that affect latency, throughput, caching, batching, scaling behavior, or duplicate work.","https:\u002F\u002Fgithub.com\u002FPolakiniO\u002FAI-Engineering-Playbook\u002Fblob\u002Fmain\u002Fskills\u002Fperformance-optimizer\u002FSKILL.md",[],[]]