platform-project-skill

name	platform-project-skill
description	Use when initializing a new *-platform project, deriving from omni-platform, upgrading an existing codebase for AI handoff, or productizing a copied public repository.
metadata	{"version":"0.6.0"}

Platform Project Skill

Route

Target	Workflow
Empty or new	references/workflow-new-project.md
Existing production code	references/workflow-existing-project.md + references/non-invasive-upgrade.md
Copied public repository	references/workflow-open-source-fork.md
README, assets, or graphify only	references/INDEX.md

When a path is provided, run scripts/inspect-project.sh <path> before choosing a route.

Hard Constraints

• Derive new projects only through scripts/create-platform-project.sh; never reconstruct the bundled template from memory.
• Existing-project upgrades are inspect-first, conservative, .gitignore-aware, and must not change business code or structure by default.
• Keep Codebase Memory project-local and opt-in. Never download its binary, register a global MCP, start watchers, or index automatically during initialization.
• Generate eight baseline Skills plus deterministic UI Profiles. Generated projects must route automatic Skill selection through their project-local manifest without global fallback, remain portable across computers, keep Handoff project-local, exclude Headroom, keep Ant Design/GSAP dependencies opt-in, and never install upstream provider hooks.
• Route HTML prototypes, wireframes, and design-system previews to the isolated Baoyu Design adaptation; keep production implementation, raster assets, and existing project stacks on their original workflows.
• Generate the five root cognition image types in equivalent zh-CN and en copies with Codex-native imagegen, then register them. Treat front/mobile/server UI and module images as optional until the owning subproject needs them.
• Before any formal raster asset, route scene planning through references/image-orchestration.md, generate five low-cost hero previews, wait for user selection, and require style_direction_done; only an explicit current-request opt-out may skip previews.
• Prefer shared PostgreSQL and Redis. Use standalone containers only when shared infrastructure is unavailable or isolation is explicit.
• README images use direct Markdown; social preview PNG must remain below 1 MiB.
• Public publishing, repository metadata, commits, tags, pushes, and releases require explicit approval.

Completion Gate

For new projects, advance only in this order:

scaffold_done -> agent_ready_done -> style_preview_done -> style_direction_done -> asset_done -> visual_acceptance_done -> validation_done -> initialization_done

Run the generated project's Agent Skill verifier with --baseline, generate and register all required images, record per-image human acceptance, then run:

scripts/validate-platform-project.sh <project-path>

Only that total validator may emit STATE=validation_done. Any failed state or unfinished asset requires a partial/blocking report, not "complete". Use references/completion-report-template.md for the final report.

Load additional rules only through references/INDEX.md as the selected route needs them.