lamina-problem-framing
SolidDesign intake — align user request to domain scope, actors, and success outcome. Not pre-fieldwork research questions.
Web & Frontend 65 stars
2 forks Updated today Apache-2.0
Install
Quality Score: 82/100
Stars 20%
Recency 20%
Frontmatter 20%
Documentation 15%
Issue Health 10%
License 10%
Description 5%
Skill Content
# Problem Framing (agent-native)
Turn a user request into a **bounded design target** before writing the active GraphVersion.
## Checklists
1. What domain entities are touched?
2. Which actors care and what outcome defines success?
3. What is explicitly out of scope?
4. Blocking vs deferred unknowns (see merge-rules intake gate).
## Anti-patterns
- **Research question theater** — "what study should we run" without a product target
- **Solution-first** — screens before domain
## Related
- [Business Context](../lamina-business-context/SKILL.md)
- [System Structure](../lamina-system-structure/SKILL.md)
Details
- Author
- aryaniyaps
- Repository
- aryaniyaps/lamina
- Created
- 3 weeks ago
- Last Updated
- today
- Language
- TypeScript
- License
- Apache-2.0
Similar Skills
Semantically similar based on skill content — not just same category
AI & Automation Solid
lamina-core
Lamina Problem Router — product design at the intersection of UX, product rules, and systems thinking.
65 Updated today
aryaniyaps Web & Frontend Solid
lamina-interview-design
Actor-walk script design — probe operations, goals, and failure modes per simulated actor. Not human moderator craft.
65 Updated today
aryaniyaps Web & Frontend Solid
lamina-product-behavior
Represented model matches domain — UI must not imply illegal states or permissions. Use when the active GraphVersion domain and screens diverge from implementation shape.
65 Updated today
aryaniyaps