원클릭으로
kmp-baseline-prompt-blueprint
Blueprint outlining the initial prompt steps for setting up the management and tracking files.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Blueprint outlining the initial prompt steps for setting up the management and tracking files.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
A visual test-driven development loop for Compose apps using Compose HotSwan for Android device testing. Navigates the live app, edits code, hot-reloads, and produces a markdown report that EMBEDS before/after screenshots so the change is shown, not just claimed.
Bootstraps a new KMP project by cloning a specified GitHub template repository into a new directory, seeding it with core AI skills, stripping its git history, and initializing a fresh workspace.
A summary of all names and descriptions of skills in the dyor/skills repository, used to guide importing relevant skills.
Guides the implementation of Firebase in a KMP project using native platform SDKs (Android/iOS) via Interface Injection, avoiding third-party KMP wrappers.
Scaffolds a complete 6-part Planning Skill (Prompt, Agent, Guide, Calculator, Validation, Hints) inside the remote `.skills/planning-skills/` directory for authoring a new chunk of orchestrated work.
Consumer-side. Imports a remote skill (single or collection) into the local `.skills/imported-skills` folder using a Python script. Can also refresh all skills using version-first, SHA-fallback drift detection. Pairs with the author-side skill `update-importable-skill`. Full lifecycle doc is bundled at `./references/IMPORTING-SKILLS-DOCUMENTATION.md`.
| name | kmp-baseline-prompt-blueprint |
| description | Blueprint outlining the initial prompt steps for setting up the management and tracking files. |
[!WARNING] This is an immutable blueprint template that is used to build the active plans. Do not execute or edit this file directly while writing code for this codebase - only for building the active plans. For active execution, use .skills/planning-skills/
I want you to initialize this new KMP project by executing the blueprint skills in the imported .skills/imported-skills/planning-skills/kmp-baseline/ directory. You must generate their corresponding codebase-specific -local files in a completely new, separate directory called .skills/planning-skills/kmp-baseline-local/. Do not write any generated files into the imported kmp-baseline directory.
Please follow these exact steps sequentially. Do not start executing the actual development tasks yet; your goal is purely to generate the management and tracking files.
Read the Blueprint Skills:
Read the sibling directories located adjacent to this prompt (inside the .skills/imported-skills/planning-skills/kmp-baseline/ folder) to understand the templates available.
CRITICAL RULE: For any skill instantiated from this kmp-baseline/ directory, if its corresponding blueprint directory contains an examples/ or resources/ folder (e.g., ../[blueprint-name]/examples/ or ../[blueprint-name]/resources/), you MUST copy those folders into the newly created local directory (e.g., [local-skill-name]/examples/ and [local-skill-name]/resources/ under .skills/planning-skills/kmp-baseline-local/).
Generate the kmp-baseline-hints-local:
Execute the instructions in ../kmp-baseline-hints-blueprint/SKILL.md to create the codebase-specific kmp-baseline-hints-local/SKILL.md file (located in .skills/planning-skills/kmp-baseline-local/kmp-baseline-hints-local/SKILL.md), which will act as the baseline for architecture rules and library versions. Don't forget to copy the examples/ folder if it exists.
Generate the kmp-baseline-guide-local:
Execute the instructions in ../kmp-baseline-guide-blueprint/SKILL.md to create the kmp-baseline-guide-local/SKILL.md file (located in .skills/planning-skills/kmp-baseline-local/kmp-baseline-guide-local/SKILL.md).
Here are the core details for the project you should use to populate the guide:
**User Action**, **Agent Action**, and **Validation** prefixes for all tasks.
Validation before moving on to step 4, ask the user verify the contents of kmp-baseline-guide-local and to say 'Proceed' when the review is complete.Generate the kmp-baseline-validation-local:
Once kmp-baseline-guide-local is created, use the instructions in ../kmp-baseline-validation-blueprint/SKILL.md to generate the kmp-baseline-validation-local/SKILL.md file (located in .skills/planning-skills/kmp-baseline-local/kmp-baseline-validation-local/SKILL.md). Tailor the multi-layered testing plan specifically to the phases and features you just outlined in the kmp-baseline-guide-local. Ask user for any information needed to create a robust validation plan.
Generate the kmp-baseline-calculator-local:
Next, use the instructions in ../kmp-baseline-calculator-blueprint/SKILL.md to parse the newly created kmp-baseline-guide-local and generate the initial kmp-baseline-calculator-local/SKILL.md file (located in .skills/planning-skills/kmp-baseline-local/kmp-baseline-calculator-local/SKILL.md) to give us our starting baseline progress report. As we work through the kmp-baseline-guide-local, we will periodically run the kmp-baseline-calculator-local to estimate how much of the work we have completed.
Generate the AGENTS.md:
Finally, use the instructions in ../kmp-baseline-agent-blueprint/SKILL.md to create or update an AGENTS.md file in the root directory that has agent instructions that prevent the agent from making mistakes. As we work with this project, we will continue to add more instructions to AGENTS.md to keep the agent working smoothly with this project.
When we begin executing kmp-baseline-guide-local, you must strictly adhere to the following rules:
**Validation** task in the guide unless you have physically run the execute-and-report-journey skill, captured the screenshots, and verified the generated report.md exists on disk. Never simulate or assume a validation step.