State prompt

Skill mskayyali/Stateful/skills/state-prompt

A way of designing software where the conditions it can be in are treated as the work, not as edge cases to handle later.

Install

npx -y skills add mskayyali/Stateful --skill state-prompt

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Rewrite a generic product-design prompt into a paste-ready prompt for one specific Stateful condition or one explicit high-risk composition of lifecycle state, interruption context, surface, and changed-data or dependency condition. Use when generating a screen, component, email, notification, or prototype from an existing map. Do not paste the whole map into a generator or use for non-stateful brand and marketing imagery.

SKILL.md

2.2 KB, as published. Nobody here has run it

State Prompt

Produce one bounded design-generation prompt from confirmed condition-map content.

Procedure

Read STATEFUL.md and state-map.json when present.
Identify:
- target lifecycle or failure condition;
- interruption/re-entry context, if any;
- target surface;
- data, time, actor, permission, and dependency facts;
- acceptance criteria and constraints.
If the user has no target, offer three risk-relevant candidates from the map. Do not invent a substitute map.
For failures, use cause to frame the response:
- user-input: coaching and correction;
- system: ownership, safe retry, and correlation when useful;
- external: dependency status and alternatives;
- policy: clear rule and permitted next action.
Include surface-specific accessibility, freshness, authentication, privacy, and action constraints.
Produce one prompt for one condition or explicit composition. Name assumptions separately.
Suggest adjacent conditions only after the paste-ready block.

Output

Condition being generated:
<lifecycle/failure × interruption × surface>

Prompt:
---
<surface and viewport>

Condition:
<what happened and what is true now>

Render and behavior:
- <observable requirement>
- <supported actions and recovery>
- <accessibility, freshness, privacy, and platform constraints>

Acceptance criteria:
- <criterion>

Output:
<single artifact and format>
---

Assumptions:
- <assumption>

Adjacent conditions worth generating:
- <condition>

Failure modes

A generic prompt with a condition name pasted on.
Omitting what happened and what is true.
Including the whole map.
Losing the target surface.
Ignoring failure cause or recovery.
Generating unsupported product decisions.