Svelte Core Best Practices
rilldata/rill
Rules for writing idiomatic Svelte 5 code: when to reach for runes like state, derived and effect, and how to handle props, attachments and bindings.
Read, write, and maintain .spec2cloud/state.json across phases and increments.
Install State Management
$ npx skills add EmeaAppGbb/spec2cloud --skill state-management -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install EmeaAppGbb/spec2cloud state-management --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/state-management .claude/skills/state-management && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "state-management" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/state-management into .claude/skills/state-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "state-management", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/state-managementType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add EmeaAppGbb/spec2cloud --skill state-management -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install EmeaAppGbb/spec2cloud state-management --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/state-management .agents/skills/state-management && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "state-management" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/state-management into .agents/skills/state-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "state-management", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add EmeaAppGbb/spec2cloud --skill state-management -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install EmeaAppGbb/spec2cloud state-management --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/state-management .cursor/skills/state-management && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "state-management" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/state-management into .cursor/skills/state-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "state-management", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/EmeaAppGbb/spec2cloud.git --path .github/skills/state-management--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add EmeaAppGbb/spec2cloud --skill state-management -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install EmeaAppGbb/spec2cloud state-management --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/state-management .gemini/skills/state-management && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "state-management" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/state-management into .gemini/skills/state-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "state-management", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install EmeaAppGbb/spec2cloud state-managementInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add EmeaAppGbb/spec2cloud --skill state-management -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/state-management .github/skills/state-management && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "state-management" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/state-management into .github/skills/state-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "state-management", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add EmeaAppGbb/spec2cloud --skill state-management -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install EmeaAppGbb/spec2cloud state-management --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/EmeaAppGbb/spec2cloud.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/state-management .opencode/skills/state-management && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "state-management" agent skill from https://github.com/EmeaAppGbb/spec2cloud/tree/vNext/.github/skills/state-management into .opencode/skills/state-management/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "state-management", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
state-management- GitHub stars
- 100
- Token cost
- ~1.5k tokens
- SKILL.md length
- 597 words
- Files
- 2 (incl. references)
- Skills in repo
- 38
- Repo updated
- First seen
- Licence
- MIT
At a glance
Read, write, and maintain .spec2cloud/state.json across phases and increments.
- Works in 4 steps: Read .spec2cloud/state.json → Parse currentPhase to determine where… → If in increment-delivery, parse… → …
- Reading project state
- SKILL.md covers Reading State, Writing State, State File Schema and Increment Object Fields, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
State Management is an agent skill from EmeaAppGbb/spec2cloud. Read, write, and maintain .spec2cloud/state.json across phases and increments. Defines the state schema, read/write protocol, and resume re-validation logic. Use when reading project state, updating state after task completion, or resuming from a previous session.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/schema.md`).
It sits in Frontend & Design, covering State management. The licence is MIT.
When your agent uses it
- Reading project state
- Updating state after task completion
- Resuming from a previous session
Example prompts
- “/state-management”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Read .spec2cloud/state.json
- Parse currentPhase to determine where you are (setup, discovery, or increment-delivery)
- If in increment-delivery, parse currentIncrement and its steps to determine what's been done and what's next
- Parse humanGates to check which approvals have been granted
What it can do on your machine
Read from SKILL.md and the folder at commit 8e76618. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
State Management loads about 1.5k tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 70 tokens; SKILL.md has 597 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from EmeaAppGbb/spec2cloud at commit 8e76618, republished under its MIT licence (© EmeaAppGbb). 597 words, ~1,498 tokens.
Download SKILL.mdSave it as
.claude/skills/state-management/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- state-management
- description
- Read, write, and maintain .spec2cloud/state.json across phases and increments. Defines the state schema, read/write protocol, and resume re-validation logic. Use when reading project state, updating state after task completion, or resuming from a previous session.
State Management
State lives in .spec2cloud/state.json. You read it at the start of every loop iteration and write it at the end.
Reading State
At the start of every loop iteration:
- Read
.spec2cloud/state.json - Parse
currentPhaseto determine where you are (setup, discovery, or increment-delivery) - If in
increment-delivery, parsecurrentIncrementand itsstepsto determine what's been done and what's next - Parse
humanGatesto check which approvals have been granted
Writing State
At the end of every loop iteration:
- Update the relevant section with the result of the task you just executed
- Update
lastUpdatedto the current ISO timestamp - Write the updated state back to
.spec2cloud/state.json
State File Schema
See references/schema.md for the full JSON schema example and field descriptions.
Increment Object Fields
| Field | Type | Description |
|---|---|---|
status | "pending" | "in-progress" | "done" | Overall increment delivery status. "done" only when Step 4 (Verify & Ship) completes. |
steps | object | Per-step status tracking: tests, contracts, implementation, verification. |
Step Object Fields
| Step | Key Fields | Description |
|---|---|---|
tests | e2eSpecs, gherkinFiles, cucumberSteps, vitestFiles | Files generated for this increment's test scaffolding. |
contracts | apiContracts, sharedTypes, infraUpdated | Contract artifacts for this increment. |
implementation | slices (api, web, integration) | Per-slice tracking with modifiedFiles, failingTests, lastTestRun, iteration. |
verification | regression, deployment, smokeTests, docs | Full regression results, deployment URL, smoke test results, docs status. |
Slice Dependencies (within implementation)
Contracts → api (api slice reads contract types)
Contracts → web (web slice reads contract types)
api + web → integration (integration requires both slices done)
integration → verification (verify requires all slices green)Brownfield State Fields
When operating in brownfield mode, the state includes additional fields for testability tracking and per-feature track assignment.
| Field | Type | Description |
|---|---|---|
brownfield.testability | "full" | "partial" | "none" | Overall testability verdict after the testability gate. |
brownfield.track | "A" | "B" | "hybrid" | Delivery track: A (testable, green baseline), B (doc-only), or hybrid (mix per feature). |
brownfield.testabilityChecklist | object | Six binary checks: canBuild, externalDepsReachable, apiExercisable, uiRenderable, devEnvExists, existingTestsRunnable. |
brownfield.featureTracks | object | Map of featureId → "A" | "B". Only present when track is "hybrid". |
brownfield.greenBaseline | object | Track A metrics: per-feature scenarios count, testsPass boolean, lastVerified ISO timestamp. |
brownfield.behavioralDocs | object | Track B metrics: per-feature scenarios count and manualChecklist item count. |
Show full SKILL.md (281 more words)Show less
Brownfield State Transitions
| Trigger | Phase | State Updates |
|---|---|---|
| Extraction complete | "B1" | currentPhase: "B1", extraction output paths recorded in brownfield.extraction |
| Spec-Enable complete | "B2" | currentPhase: "B2", brownfield.prdGenerated: true, brownfield.frdCount: N |
| Testability gate complete | "B3" | currentPhase: "B3", brownfield.testability, brownfield.track, brownfield.testabilityChecklist recorded |
| Track A baseline green | (still B3) | brownfield.greenBaseline.features populated with per-feature test results |
| Track B docs complete | (still B3) | brownfield.behavioralDocs.features populated with per-feature scenario/checklist counts |
| Path selection (human gate) | "assessment" | brownfield.selectedPaths array recorded (e.g., ["modernize", "security"]) |
| Assessment + planning done | "increment-delivery" | Increments generated, incrementPlan populated, delivery proceeds track-aware |
When track is "hybrid", each increment in Phase 2 inherits its track from featureTracks. Track A increments follow the full test → contract → implement → verify cycle. Track B increments follow a doc-only path (behavioral docs + manual checklists instead of automated green baselines).
On Resume
- Read
.spec2cloud/state.json - Determine current increment and current step within it
- Re-validate by running the appropriate test suite:
- Tests step: verify test files exist and compile
- Implementation step: run tests for the current slice, compare to state
- Verification step: check deployment status
- If results match state → continue from where you left off
- If results differ → update state to reflect reality, then continue
Mandatory Completion Checklist
The orchestrator MUST verify ALL of the following after every state write:
-
.spec2cloud/state.jsonis valid JSON (parseable without errors) -
currentPhasereflects the actual phase the orchestrator is in -
currentIncrementand increment step match the work just completed -
lastUpdatedtimestamp is current - No fields are null/undefined that downstream skills depend on (e.g.,
adrs.nextNumber,incrementPlan) - State file is committed alongside the artifacts it describes (not orphaned)
BLOCKING: If state.json is invalid or inconsistent with actual artifacts, the resume skill will reconstruct the wrong position. Fix state before proceeding.
© EmeaAppGbb, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in .github/skills/state-management of EmeaAppGbb/spec2cloud.
- SKILL.md
- references/schema.md
Open the folder on GitHubat commit 8e76618
Compare with similar skills
State Management next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| State Management this skillEmeaAppGbb/spec2cloud | 100 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Svelte Core Best Practicesrilldata/rill | 2.9k | 4 repos | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Dify Component Writing Guidelanggenius/dify | 158k | — | ~626 | Automated safety check: Pass | Custom licence | |
| React State Managementinvolvex/youtube-music-cli | 456 | 13 repos | ~3k | Automated safety check: Pass | MIT | |
| GPUI Kit Desktop App GuideAprilNEA/OpenLogi | 23k | — | ~5.5k | Automated safety check: Pass | Apache-2.0 | |
| Pierre Theming Librarypierrecomputer/pierre | 6.2k | — | ~661 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Dify Component Writing Guide
langgenius/dify
Use when implementing or refactoring React/TypeScript components and the task requires decisions about component ownership, feature boundaries, state, data…
React State Management
involvex/youtube-music-cli
Master modern React state management with Redux Toolkit, Zustand, Jotai, and React Query.
GPUI Kit Desktop App Guide
AprilNEA/OpenLogi
Guides building Rust desktop apps with the gpui-kit crate, covering component selection, state ownership, theming and overlays, plus normative GPUI coding rules.
Pierre Theming Library
pierrecomputer/pierre
Explains how to use the @pierre/theming package to list, resolve, select, switch and persist themes, with controller, color and React references.
Frontend Patterns
kurealnum/dotfiles
Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.
More from EmeaAppGbb/spec2cloud
All 38 skills in this repoAzure Deployment
EmeaAppGbb/spec2cloud
Provision Azure infrastructure, deploy to Azure Container Apps, and verify via smoke tests.
Contract Generation
EmeaAppGbb/spec2cloud
Generate API contracts, shared TypeScript types, and infrastructure resource definitions from Gherkin scenarios and test files.
Ddd Modeling
EmeaAppGbb/spec2cloud
Create Domain-Driven Design proposals from product specs or brownfield extraction outputs.
Implementation
EmeaAppGbb/spec2cloud
Write application code to make failing tests pass using contract-driven, slice-based architecture.
Spec Refinement
EmeaAppGbb/spec2cloud
Review PRDs and FRDs through product and technical lenses. An agent skill from EmeaAppGbb/spec2cloud.
Tech Stack Resolution
EmeaAppGbb/spec2cloud
Identify, research, and resolve every technology needed by the application.
Related
Categories
Questions about State Management
What does State Management do?
Read, write, and maintain .spec2cloud/state.json across phases and increments. State Management is an agent skill from EmeaAppGbb/spec2cloud.json across phases and increments.
When should I use State Management?
State Management fits situations like: reading project state; updating state after task completion; resuming from a previous session.
How do I install State Management in Claude Code?
Run `npx skills add EmeaAppGbb/spec2cloud --skill state-management -a claude-code`. Or copy the skill folder (.github/skills/state-management in EmeaAppGbb/spec2cloud) into .claude/skills/state-management in your project. Claude Code loads it when a task matches its description.
How do I install State Management in Codex?
Run `npx skills add EmeaAppGbb/spec2cloud --skill state-management -a codex`. Or copy the skill folder (.github/skills/state-management in EmeaAppGbb/spec2cloud) into .agents/skills/state-management in your project. Codex loads it when a task matches its description.
Can I use State Management in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add EmeaAppGbb/spec2cloud --skill state-management -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/state-management, .gemini/skills/state-management, .github/skills/state-management and .opencode/skills/state-management in your project.
What does State Management need to run?
SKILL.md names no scripts, command-line tools or credentials: State Management is instructions for the agent only.
Does State Management access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is State Management safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does State Management use?
State Management is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does State Management use?
About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.2k tokens, read only when the agent opens those files.
What are the alternatives to State Management?
Skills that share tags, products or a category with State Management: Svelte Core Best Practices (rilldata/rill, 2.9k stars), Dify Component Writing Guide (langgenius/dify, 158k stars), React State Management (involvex/youtube-music-cli, 456 stars) and GPUI Kit Desktop App Guide (AprilNEA/OpenLogi, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains State Management?
EmeaAppGbb (a GitHub organization) maintains it in EmeaAppGbb/spec2cloud, which has 100 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on April 16, 2026.
Source: EmeaAppGbb/spec2cloud on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.