메뉴
Choose between React Native and Apple-native for a digital health app, clone the matching Spezi starter template, and move existing planning briefs into the cloned repo so the coding agent has full context for implementation.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Turn planning outputs into a milestone-based implementation plan that sequences features, maps them to available packages or modules, and hands off to a coding agent for implementation.
Walk through the full process of building a digital health app — from planning to implementation.
Set up and maintain a persistent, LLM-managed knowledge base for a digital health project — turning clinical observations, papers, interviews, and planning docs into a compounding, interlinked wiki.
Guide a user through Stanford Biodesign's needs-finding process to define, scope, and refine a rigorous health-app need statement without jumping prematurely to solutions.
Plan healthcare privacy, research, and regulatory compliance for a digital health product, including HIPAA, IRB, FDA, GDPR, governance, and operational controls.
Plan a digital health study or research protocol, including enrollment, consent, data collection, assessment schedules, study operations, and outcome measures.
| name | spezi-platform-selection |
| description | Choose between React Native and Apple-native for a digital health app, clone the matching Spezi starter template, and move existing planning briefs into the cloned repo so the coding agent has full context for implementation. |
Use this skill when a user has finished planning, wants to start from a Spezi template, and is ready to build. It chooses between React Native and Apple-native based on the planning briefs, clones the matching Spezi starter template, and moves the existing docs/planning/ and docs/implementation-plan.md into the cloned repo so the coding agent has full context.
This skill should run after the other planning skills, not before — the platform choice is informed by what the planning revealed (HealthKit needs, cross-platform requirements, etc.).
Skip this skill if the user is not adopting a Spezi template — for example, they're extending an existing app, using a different framework (Flutter, web, etc.), or want full control over scaffolding. The planning briefs and implementation plan work just as well in any codebase; the user can hand them to their coding agent directly.
Read setup-guide.md before making the recommendation.
Ask concise questions that reveal whether the app is primarily:
Confirm:
Read platform-decision.md before deciding.
Choose React Native when:
Choose Apple-native when:
After deciding on a platform, guide the user through the matching setup steps in setup-guide.md before cloning and implementation.
Make sure the user is clear whether they want:
Use the bundled clone helper instead of writing ad hoc clone commands:
scripts/clone-template.sh react-native <destination>scripts/clone-template.sh apple-native <destination>If the current working directory contains a docs/planning/ directory or a docs/implementation-plan.md produced by the other planning skills, move them into the cloned repository so the coding agent picks up the full plan from the right place:
mv docs/planning <destination>/docs/planning
mv docs/implementation-plan.md <destination>/docs/implementation-plan.md
Confirm with the user before moving. If the cloned repo already contains a docs/planning/ directory, merge rather than overwrite.
After the move:
End with a short summary containing:
docs/implementation-plan.md