Inspired Applied Learning Platform

A digital coaching companion for teachers after in-person professional development. It measures and drives behavioral change (did the teacher apply the strategy, how fast, how many times to mastery) — not course completion. Framing question for every feature: “How do we reduce the time between learning and improved practice?”

Key docs

• plans/alp-platform-implementation-plan.md — reviewed v1 implementation plan (autoplan: CEO + Design + Eng).
• knowledge-tree/ — concepts, open questions, ideas, reference synthesized from the source docs.
• source-docs/ — original v3 workflow recommendations + dashboard user stories + flowchart images.
• DESIGN.md — the design system. Read it before any visual or UI work.

Design System

Always read DESIGN.md before making any visual or UI decisions. All font choices, colors, spacing, and aesthetic direction are defined there. Do not deviate without explicit user approval. In QA mode, flag any code that doesn’t match DESIGN.md.

The trust posture is design law: no scores / percentages / pass-fail / completion rings; progress is narrated, not quantified; the strategist view is “cohort weather,” not a watchlist; nudges are care language, never deadlines.

Skill routing

When the user’s request matches an available skill, invoke it via the Skill tool. When in doubt, invoke the skill. - Product ideas/brainstorming → invoke /office-hours - Strategy/scope → invoke /plan-ceo-review - Architecture → invoke /plan-eng-review - Design system/plan review → invoke /design-consultation or /plan-design-review - Full review pipeline → invoke /autoplan - Bugs/errors → invoke /investigate - QA/testing site behavior → invoke /qa or /qa-only - Code review/diff check → invoke /review - Visual polish → invoke /design-review - Ship/deploy/PR → invoke /ship or /land-and-deploy - Save progress → invoke /context-save - Resume context → invoke /context-restore