Skills & knowledge
How OpenV2 skills and per-project knowledge guide the AI builder.
OpenV2 uses three layers of AI guidance: platform skills (global), project knowledge (per app), and account memory (per user).
Platform skills
Skills are specialized instruction packs bundled from skills/*/SKILL.md. The AI sees a catalog of all skills in every chat and loads full skill content on demand.
Available skills
| Skill | Purpose |
|---|---|
| native-layout-contract | Mobile layout, routing, and screen structure rules |
| theme-docs | Theme tokens, colors, and styling conventions |
| ui-components | Reusable UI patterns |
| visual-effects | Animations and visual polish |
| image-rules | Image handling and asset guidelines |
| monetization | In-app purchases via RevenueCat |
| design-from-sketch | Interpret wireframe sketches |
| debug-and-fix | Diagnose and fix errors |
You do not need to mention skills manually — the AI loads them when relevant. You can also ask: "Use the monetization skill to add a paywall."
Project knowledge
Knowledge (V2 Cloud dashboard → Knowledge) stores per-project agent instructions in PROJECT_KNOWLEDGE.md. Use it for rules that apply only to this app:
- Brand voice and naming
- Feature priorities
- "Always use local storage for drafts"
- API endpoints or business rules
Knowledge persists in your project workspace and is included in AI context.
Account memory
Account memory (dashboard → Memory) stores facts about you across all projects — preferences, language, recurring constraints. The agent can append to it with the remember tool. Unlike knowledge, it is not stored in the project workspace.
Skills vs. knowledge vs. memory
| Skills | Knowledge | Account memory | |
|---|---|---|---|
| Scope | Platform-wide | Single project | Your OpenV2 account |
| Maintained by | OpenV2 | You | You (+ agent remember) |
| Examples | Layout contracts, monetization | "Never use PocketBase for guest mode" | "Always reply in Romanian" |