App Artifact Scaffold

Create app artifact templates

by wondelai · MIT license · ★ 2,235 on GitHub · updated Sep 10

Create app artifact templates cover

Skeletons this metaskill creates in the user's docs/ folder.

# create-app artifact templates

Skeletons this metaskill creates in the user's docs/ folder. Extend-only artifacts (CUSTOMER.md, STRATEGY.md, TECH-DEBT.md) are governed by the section headings named in each phase, not skeletons here.

## docs/CREATE-APP-PLAN.md (tracker)

```markdown
# Create an App Plan

## Context
Intake answers, date started, project specifics. Note whether shipping native iOS (gates Phase 8).

## Phase Status
| Phase | Skill | Status | Artifact | Date |
|---|---|---|---|---|
| 1 | lean-startup | pending | PRODUCT.md, EXPERIMENTS.md | |
| 2 | design-sprint | pending | DESIGN.md, EXPERIMENTS.md | |
| 3 | clean-architecture | pending | ARCHITECTURE.md | |

Overview

Skeletons this metaskill creates in the user's docs/ folder. Extend-only artifacts (CUSTOMER.md, STRATEGY.md, TECH-DEBT.md) are governed by the section headings named in each phase, not skeletons here.

Manual install (npx, ZIP)
Claude Codenpx skills add wondelai/skills --skill create-app-artifact-templates -g -a claude-code
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • artifact-templates.md3.7 KB
Read artifact-templates.md here
wondelai/main1 file
artifact-templates.md
Show the full text155 lines

create-app artifact templates

Skeletons this metaskill creates in the user's docs/ folder. Extend-only artifacts (CUSTOMER.md, STRATEGY.md, TECH-DEBT.md) are governed by the section headings named in each phase, not skeletons here.

docs/CREATE-APP-PLAN.md (tracker)

# Create an App Plan

## Context
Intake answers, date started, project specifics. Note whether shipping native iOS (gates Phase 8).

## Phase Status
| Phase | Skill | Status | Artifact | Date |
|---|---|---|---|---|
| 1 | lean-startup | pending | PRODUCT.md, EXPERIMENTS.md | |
| 2 | design-sprint | pending | DESIGN.md, EXPERIMENTS.md | |
| 3 | clean-architecture | pending | ARCHITECTURE.md | |
| 4 | domain-driven-design | pending | ARCHITECTURE.md | |
| 5 | clean-code | pending | TESTING.md | |
| 6 | pragmatic-programmer | pending | TESTING.md, TECH-DEBT.md | |
| 7 | system-design | pending | ARCHITECTURE.md | |
| 8 | ios-hig-design | pending | DESIGN.md | |
| 9 | 37signals-way | pending | PRODUCT.md, STRATEGY.md | |
| 10 | software-design-philosophy | pending | TECH-DEBT.md, ARCHITECTURE.md | |
Statuses: pending · in-progress · awaiting-evidence · done · deferred: <reason> · skipped: <reason>

## Key Decisions
| Date | Phase | Decision | Rationale |
|---|---|---|---|

## Next Actions
- [ ] action (owner, due)

docs/PRODUCT.md

# Product

## Vision
One paragraph.

## MVP Definition
Type, scope, what it deliberately excludes.

## Outcome Roadmap
| Outcome / problem | Job served | Priority | Status |
|---|---|---|---|

## Opportunity Solution Tree Notes

## Hook Model
Trigger → Action → Variable reward → Investment; weakest phase.

## Activation & Retention Plan
| Friction / moment | Fix | Owner | Status |
|---|---|---|---|

## Discovery Cadence
Weekly touchpoint plan.

docs/EXPERIMENTS.md

# Experiments

## Experiment Cards
### EXP-001 — [name]
- Hypothesis: We believe [outcome] if [who] [does what] because [reason]
- Type: sprint / smoke test / concierge / painted door / A-B
- Primary metric & threshold (pre-committed):
- Guardrail metric:
- Decision rule (pivot / persevere / iterate):
- Result & verdict:

## Experiment Backlog
| Idea | ICE (impact/confidence/ease) | Status |
|---|---|---|

docs/ARCHITECTURE.md

# Architecture

## System Context
What the system does, key integrations, load reality (back-of-envelope numbers).

## Layer Map & Dependency Rule
Layers, what depends on what, current violations.
| Violation | Location | Fix | Status |
|---|---|---|---|

## Bounded Contexts & Context Map
Contexts, relationships, anti-corruption layers.

## Domain Glossary (Ubiquitous Language)
| Term | Meaning | Code name |
|---|---|---|

## Data & Storage Decisions
Data models, storage engines, isolation levels, replication, system-of-record vs derived data.

## Decision Log
| Date | Decision | Why | Alternatives rejected |
|---|---|---|---|

docs/TESTING.md

# Testing

## Test Strategy
Pyramid, tooling, what "green" gates.

## Safety Net Map
| Module | Pinned behaviors | Test files | Gaps |
|---|---|---|---|

## Characterization Backlog
- [ ] module (risk, priority)

## CI Gates

docs/DESIGN.md

# Design System

## Design Direction
Signature moment, personality, references.

## Typography
Typefaces, scale, measure, line height, loading strategy.

## Tokens
Spacing scale · color palette (shades, tinted grays) · shadows.

## Components
| Component | Decision | Status |
|---|---|---|

## UX Audit Findings
| Issue | Heuristic | Severity (0-4) | Fix | Status |
|---|---|---|---|---|

## Microinteraction Inventory
| Interaction | Trigger/Rules/Feedback/Loops | Fix | Status |
|---|---|---|---|
1# create-app artifact templates
2 
3Skeletons this metaskill creates in the user's docs/ folder. Extend-only artifacts (CUSTOMER.md, STRATEGY.md, TECH-DEBT.md) are governed by the section headings named in each phase, not skeletons here.
4 
5## docs/CREATE-APP-PLAN.md (tracker)
6 
7```markdown
8# Create an App Plan
9 
10## Context
11Intake answers, date started, project specifics. Note whether shipping native iOS (gates Phase 8).
12 
13## Phase Status
14| Phase | Skill | Status | Artifact | Date |
15|---|---|---|---|---|
16| 1 | lean-startup | pending | PRODUCT.md, EXPERIMENTS.md | |
17| 2 | design-sprint | pending | DESIGN.md, EXPERIMENTS.md | |
18| 3 | clean-architecture | pending | ARCHITECTURE.md | |
19| 4 | domain-driven-design | pending | ARCHITECTURE.md | |
20| 5 | clean-code | pending | TESTING.md | |
21| 6 | pragmatic-programmer | pending | TESTING.md, TECH-DEBT.md | |
22| 7 | system-design | pending | ARCHITECTURE.md | |
23| 8 | ios-hig-design | pending | DESIGN.md | |
24| 9 | 37signals-way | pending | PRODUCT.md, STRATEGY.md | |
25| 10 | software-design-philosophy | pending | TECH-DEBT.md, ARCHITECTURE.md | |
26Statuses: pending · in-progress · awaiting-evidence · done · deferred: <reason> · skipped: <reason>
27 
28## Key Decisions
29| Date | Phase | Decision | Rationale |
30|---|---|---|---|
31 
32## Next Actions
33- [ ] action (owner, due)
34```
35 
36## docs/PRODUCT.md
37 
38```markdown
39# Product
40 
41## Vision
42One paragraph.
43 
44## MVP Definition
45Type, scope, what it deliberately excludes.
46 
47## Outcome Roadmap
48| Outcome / problem | Job served | Priority | Status |
49|---|---|---|---|
50 
51## Opportunity Solution Tree Notes
52 
53## Hook Model
54Trigger → Action → Variable reward → Investment; weakest phase.
55 
56## Activation & Retention Plan
57| Friction / moment | Fix | Owner | Status |
58|---|---|---|---|
59 
60## Discovery Cadence
61Weekly touchpoint plan.
62```
63 
64## docs/EXPERIMENTS.md
65 
66```markdown
67# Experiments
68 
69## Experiment Cards
70### EXP-001 — [name]
71- Hypothesis: We believe [outcome] if [who] [does what] because [reason]
72- Type: sprint / smoke test / concierge / painted door / A-B
73- Primary metric & threshold (pre-committed):
74- Guardrail metric:
75- Decision rule (pivot / persevere / iterate):
76- Result & verdict:
77 
78## Experiment Backlog
79| Idea | ICE (impact/confidence/ease) | Status |
80|---|---|---|
81```
82 
83## docs/ARCHITECTURE.md
84 
85```markdown
86# Architecture
87 
88## System Context
89What the system does, key integrations, load reality (back-of-envelope numbers).
90 
91## Layer Map & Dependency Rule
92Layers, what depends on what, current violations.
93| Violation | Location | Fix | Status |
94|---|---|---|---|
95 
96## Bounded Contexts & Context Map
97Contexts, relationships, anti-corruption layers.
98 
99## Domain Glossary (Ubiquitous Language)
100| Term | Meaning | Code name |
101|---|---|---|
102 
103## Data & Storage Decisions
104Data models, storage engines, isolation levels, replication, system-of-record vs derived data.
105 
106## Decision Log
107| Date | Decision | Why | Alternatives rejected |
108|---|---|---|---|
109```
110 
111## docs/TESTING.md
112 
113```markdown
114# Testing
115 
116## Test Strategy
117Pyramid, tooling, what "green" gates.
118 
119## Safety Net Map
120| Module | Pinned behaviors | Test files | Gaps |
121|---|---|---|---|
122 
123## Characterization Backlog
124- [ ] module (risk, priority)
125 
126## CI Gates
127```
128 
129## docs/DESIGN.md
130 
131```markdown
132# Design System
133 
134## Design Direction
135Signature moment, personality, references.
136 
137## Typography
138Typefaces, scale, measure, line height, loading strategy.
139 
140## Tokens
141Spacing scale · color palette (shades, tinted grays) · shadows.
142 
143## Components
144| Component | Decision | Status |
145|---|---|---|
146 
147## UX Audit Findings
148| Issue | Heuristic | Severity (0-4) | Fix | Status |
149|---|---|---|---|---|
150 
151## Microinteraction Inventory
152| Interaction | Trigger/Rules/Feedback/Loops | Fix | Status |
153|---|---|---|---|
154```
155 
View all files on GitHub →

Details

Updated
Sep 10, 2026
License
MIT
Stars on the repo
★ 2,235
Checked
Source
wondelai/skills ↗
Creator
wondelai · 319 listings
View creator

Similar versions (1)

Other versions of this skill by wondelai. They do nearly the same job, so we list this one and link the rest.

Similar skills

See all →
AgentPhase 2: Foundation Scaffoldingmsitarzewski/agency-agents · by msitarzewski> Duration: 3-5 days | Agents: 6 | Gate Keepers: DevOps Automator + Evidence Collector★ 154k GitHub starsAgentNEXUS Network Frameworkmsitarzewski/agency-agents · by msitarzewski> NEXUS transforms The Agency's independent AI specialists into a synchronized intelligence network. This is not a prompt collection — it…★ 154k GitHub starsSkillAnsoff Matrix Generatorphuryn/pm-skills · by phurynGenerate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.★ 26.6k GitHub starsSkillArchitecture Advisorshadcn/improve · by shadcnSurvey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.★ 9.2k GitHub starsSkillCareer Skills TranslatorParamchoudhary/ResumeSkills · by ParamchoudharyTranslate skills from one industry to another, identify transferable skills★ 2.4k GitHub starsSkillMarketing Skills CollectionLeoYeAI/openclaw-marketing-skills · by LeoYeAIA collection of 37 battle-tested marketing skills for OpenClaw agents. Use when you want to install or reference any marketing skill including: CRO (page-cro, signup-flow-cro, onboarding-cro, form-cro, popup-cro, paywall-upgrade-cro), copywriting, copy-editing, cold-email, email-sequence, social-content, seo-audit, ai-seo, programmatic-seo, site-architecture, schema-markup, content-strategy, paid-ads, ad-creative, ab-test-setup, analytics-tracking, referral-program, free-tool-strategy, churn-prevention, revops, sales-enablement, launch-strategy, pricing-strategy, competitor-alternatives, marketing-ideas, marketing-psychology, lead-magnets, product-marketing-context, and data connectors (google-ads-connect, search-console-connect, meta-ads-connect, x-twitter-connect). Start with product-marketing-context to set up your product context document, then use any other skill naturally. Powered by MyClaw.ai.★ 1k GitHub stars

More from wondelai

SkillSoftware Design Philosophywondelai/skills · by wondelaiManage software complexity through deep modules, information hiding, and strategic programming. Use when the user mentions "module design", "API too complex", "shallow class", "complexity budget", "strategic vs tactical", "deep module", "information leakage", "pass-through method", "this code is over-engineered", or "simplify this design". Also trigger when reviewing an interface for simplicity, evaluating whether an abstraction is pulling its weight, deciding whether a comment is worth writing, or choosing between general-purpose and special-purpose approaches. Covers deep vs shallow modules, red flags for complexity, and comments as design documentation. For code quality, see clean-code. For architecture boundaries, see clean-architecture.★ 2.2k GitHub starsSkillActionable Metrics Guidewondelai/skills · by wondelaiMetrics are the language of validated learning. The wrong metrics create the illusion of progress while the startup drifts toward failure.…★ 2.2k GitHub starsSkillAdvertising Mediawondelai/skills · by wondelaiAdvertising media is the vehicle that carries your message to your target market. Choosing the right media is not about what is trendy — it…★ 2.2k GitHub starsSkillAffordance Designwondelai/skills · by wondelaiAn affordance is a relationship between an object and a person that determines how the object could possibly be used. A chair affords…★ 2.2k GitHub starsSkillLean UX in Agile Teamswondelai/skills · by wondelaiLean UX was designed to work inside Agile development teams, not alongside them. The central mechanism is dual-track agile, where a…★ 2.2k GitHub starsSkillAMP Framework Practitionerwondelai/skills · by wondelaiThis reference translates the AMP framework from theory into practice across six domains: product gamification, team management,…★ 2.2k GitHub stars