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.
A specialized skill for the branch-architect agent covering branching logic.
Install Branching Logic
$ npx skills add revfactory/harness-100 --skill branching-logic -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install revfactory/harness-100 branching-logic --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/revfactory/harness-100.git skills-src && mkdir -p .claude/skills && cp -r skills-src/en/05-game-narrative/.claude/skills/branching-logic .claude/skills/branching-logic && 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 "branching-logic" agent skill from https://github.com/revfactory/harness-100/tree/main/en/05-game-narrative/.claude/skills/branching-logic into .claude/skills/branching-logic/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "branching-logic", 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/revfactory/harness-100/tree/main/en/05-game-narrative/.claude/skills/branching-logicType 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 revfactory/harness-100 --skill branching-logic -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install revfactory/harness-100 branching-logic --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .agents/skills && cp -r skills-src/en/05-game-narrative/.claude/skills/branching-logic .agents/skills/branching-logic && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "branching-logic" agent skill from https://github.com/revfactory/harness-100/tree/main/en/05-game-narrative/.claude/skills/branching-logic into .agents/skills/branching-logic/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "branching-logic", 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 revfactory/harness-100 --skill branching-logic -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install revfactory/harness-100 branching-logic --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/en/05-game-narrative/.claude/skills/branching-logic .cursor/skills/branching-logic && 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 "branching-logic" agent skill from https://github.com/revfactory/harness-100/tree/main/en/05-game-narrative/.claude/skills/branching-logic into .cursor/skills/branching-logic/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "branching-logic", 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/revfactory/harness-100.git --path en/05-game-narrative/.claude/skills/branching-logic--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 revfactory/harness-100 --skill branching-logic -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install revfactory/harness-100 branching-logic --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/en/05-game-narrative/.claude/skills/branching-logic .gemini/skills/branching-logic && 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 "branching-logic" agent skill from https://github.com/revfactory/harness-100/tree/main/en/05-game-narrative/.claude/skills/branching-logic into .gemini/skills/branching-logic/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "branching-logic", 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 revfactory/harness-100 branching-logicInstalls 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 revfactory/harness-100 --skill branching-logic -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .github/skills && cp -r skills-src/en/05-game-narrative/.claude/skills/branching-logic .github/skills/branching-logic && 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 "branching-logic" agent skill from https://github.com/revfactory/harness-100/tree/main/en/05-game-narrative/.claude/skills/branching-logic into .github/skills/branching-logic/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "branching-logic", 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 revfactory/harness-100 --skill branching-logic -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install revfactory/harness-100 branching-logic --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/revfactory/harness-100.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/en/05-game-narrative/.claude/skills/branching-logic .opencode/skills/branching-logic && 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 "branching-logic" agent skill from https://github.com/revfactory/harness-100/tree/main/en/05-game-narrative/.claude/skills/branching-logic into .opencode/skills/branching-logic/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "branching-logic", 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
branching-logic- GitHub stars
- 1.3k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 397 words
- Files
- 1
- Skills in repo
- 464
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A specialized skill for the branch-architect agent covering branching logic.
- Works in 6 steps: Bottleneck Structure (Hub-and-Spoke) → Parallel Paths → Branching Tree → …
- Multiple endings
- SKILL.md covers Why Branching Logic Matters, 6 Branching Structure Patterns, Flag System Design and Ending Architecture, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Branching Logic is an agent skill from revfactory/harness-100. A specialized skill for the branch-architect agent covering branching logic. Provides branching structure patterns, flag system design, ending architecture, and state management methodology. Use for 'branch design,' 'multiple endings,' 'flag systems,' 'branching structures,' and similar topics.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering State management. The licence is Apache-2.0.
When your agent uses it
- Multiple endings
- Branching structures
Example prompts
- “branch design,”
- “multiple endings,”
- “flag systems,”
- “/branching-logic”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 8e8d35c. 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
Branching Logic loads about 1.4k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 397 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 revfactory/harness-100 at commit 8e8d35c, republished under its Apache-2.0 licence (© revfactory). 397 words, ~1,354 tokens.
Download SKILL.mdSave it as
.claude/skills/branching-logic/SKILL.md (or your agent's skills folder).- name
- branching-logic
- description
- A specialized skill for the branch-architect agent covering branching logic. Provides branching structure patterns, flag system design, ending architecture, and state management methodology. Use for 'branch design,' 'multiple endings,' 'flag systems,' 'branching structures,' and similar topics.
Branching Logic — Branching Logic Design Methodology
Specialized knowledge used by the branch-architect agent when designing branching structures, endings, and flag systems.
Why Branching Logic Matters
Branching is the key differentiator that separates game narrative from novels and film. However, the more branches there are, the more production costs increase exponentially. The art lies in making players feel significant variation with fewer branches.
6 Branching Structure Patterns
1. Bottleneck Structure (Hub-and-Spoke)
A
/ \
B C <- Branch
\ /
D <- Bottleneck (convergence)
/ \
E F <- Re-branch
\ /
G <- Bottleneck- Advantage: Freedom of choice within a feasible production scope
- Key Point: All paths converge at bottleneck points, but the manner of convergence must differ
- Suited For: Most commercial RPGs (The Witcher 3, Mass Effect)
2. Parallel Paths
A -> B -> C -> D (Route 1)
A -> E -> F -> D (Route 2)
A -> G -> H -> D (Route 3)- Advantage: High replay value
- Disadvantage: Requires 3x the content
- Suited For: Short games, visual novels
3. Branching Tree
A
/|\
B C D
/| |\
E F G H- Advantage: Intuitive, easy to design
- Disadvantage: Ending count explosion (2^n), sparse late-game content
- Suited For: Short interactive fiction
4. Folding Structure (Delayed Consequences)
Choice Moment ... Result Manifestation
Choice at A -> Passes through B, C, D -> Result appears at E- Advantage: Big impact with few branches, "my choice mattered" feeling
- Key Point: Set a flag and trigger it much later
- Suited For: Long RPGs, episodic games
5. State Accumulation Structure
Choice 1: Honor +10 / Infamy +10
Choice 2: Honor +5 / Infamy +5
...
At threshold: Ending A (Honor 70+) / B (Infamy 70+) / C (Neutral)- Advantage: The sum of actions determines the outcome, not a single choice
- Key Point: Players naturally accumulate their tendencies
- Suited For: RPGs with morality systems (inFamous, Fable)
6. Hybrid Structure
Real games combine the above patterns:
- Main Story: Bottleneck structure (controllable)
- Sub Quests: Branching tree (independent, short)
- Relationship System: State accumulation (NPC affinity)
- Key Choices: Folding (delayed consequences)
Flag System Design
Show full SKILL.md (158 more words)Show less
Flag Naming Convention
[Category]_[Subject]_[State]
Examples:
QUEST_bandit_camp_destroyed — Quest-related
REL_npc_aria_friendship_high — Relationship-related
WORLD_bridge_repaired — World state
PLAYER_has_ancient_sword — Player possession
STORY_chapter2_twist_revealed — Story progression
MORAL_saved_village — Moral choiceFlag Types
| Type | Value Format | Usage | Example |
|---|---|---|---|
| Boolean | true/false | Event occurrence | QUEST_dragon_slain = true |
| Counter | Integer | Cumulative actions | MORAL_mercy_count = 3 |
| Enum | String | Path selection | FACTION_chosen = "rebels" |
| Timestamp | Game time | Time-limited quests | QUEST_deadline = day_30 |
Flag Dependency Matrix
Manage all flags needed for branch decisions in a matrix:
| Branch Point | Required Flags | Condition | Result |
|-------------|---------------|-----------|--------|
| CH3_Battle | REL_aria >= 50 AND QUEST_sword = true | Met | Aria joins |
| CH3_Battle | REL_aria < 50 OR QUEST_sword = false | Not met | Solo combat |Ending Architecture
Ending Classification
| Type | Achievement Condition | Target Player Percentage |
|---|---|---|
| Standard Ending | Main quests complete | 70-80% |
| Best Ending | Standard + key side quests + max relationships | 15-20% |
| Worst Ending | Accumulated critical choices | 5-10% |
| Hidden Ending | Special condition combinations | 1-3% |
| True Ending | Second playthrough + hidden conditions | 0.5-1% |
Ending Satisfaction Rules
- Every ending must have closure — even a "bad ending" should be narratively complete
- The best ending should not be too easy — rewards proportional to effort
- Hidden endings must have hints — completely blind discovery leads to dissatisfaction
- Post-ending summary: A "choice results" screen showing the player's key choices and outcomes
Branch Testing: Path Simulation
Document and verify all possible paths:
Path 1 (Path of Justice): A->B->D->F->Best Ending
- Flags: MORAL_good=5, REL_aria=80, QUEST_all_done=true
- Missing Content: None
- Plot Holes: None
Path 2 (Path of Pragmatism): A->C->D->G->Standard Ending
- Flags: MORAL_neutral=3, REL_aria=40
- Missing Content: Aria romance sub-quest
- Plot Holes: Conditional branch needed when Aria is mentioned in CH4
Path 3 (Path of Destruction): A->C->E->H->Worst Ending
- Flags: MORAL_evil=5, REL_aria=-20
- Plot Holes: None© revfactory, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in en/05-game-narrative/.claude/skills/branching-logic of revfactory/harness-100.
Open the folder on GitHubat commit 8e8d35c
Compare with similar skills
Branching Logic 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 |
|---|---|---|---|---|---|---|
| Branching Logic this skillrevfactory/harness-100 | 1.3k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| 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 | |
| Pierre Theming Librarypierrecomputer/pierre | 6.3k | — | ~661 | Automated safety check: Pass | Apache-2.0 | |
| Frontend Patternskurealnum/dotfiles | 290 | 19 repos | ~3.7k | Automated safety check: Pass | None |
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.
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.
LobeHub Data Fetching Layers
lobehub/lobehub
Explains how LobeHub client code fetches data through services, SWR store hooks and cache keys, and when to avoid useEffect fetching or duplicated state.
More from revfactory/harness-100
All 464 skills in this repoAnti Bot Analyzer
revfactory/harness-100
A skill for analyzing website anti-bot defense mechanisms and developing legitimate evasion strategies.
API Error Design Patterns
revfactory/harness-100
Reference for designing how an API reports failures: structured error codes, response shapes, client-friendly messages, an error catalog and retry or fallback advice.
API Security Checklist
revfactory/harness-100
Walks a backend-dev agent through OWASP API Top 10 checks, authentication and authorization patterns, and defense code during API design.
Arg Parser Generator
revfactory/harness-100
Methodology for systematically designing and generating CLI tool argument parser structures.
Audience Segmentation
revfactory/harness-100
Audience segmentation skill used by the analyst and curator agents.
Audio Storytelling
revfactory/harness-100
Audio storytelling skill used by the podcast scriptwriter and show note editor.
Related
Categories
Questions about Branching Logic
What does Branching Logic do?
A specialized skill for the branch-architect agent covering branching logic. Branching Logic is an agent skill from revfactory/harness-100. A specialized skill for the branch-architect agent covering branching logic.
When should I use Branching Logic?
Branching Logic fits situations like: multiple endings; branching structures.
How do I install Branching Logic in Claude Code?
Run `npx skills add revfactory/harness-100 --skill branching-logic -a claude-code`. Or copy the skill folder (en/05-game-narrative/.claude/skills/branching-logic in revfactory/harness-100) into .claude/skills/branching-logic in your project. Claude Code loads it when a task matches its description.
How do I install Branching Logic in Codex?
Run `npx skills add revfactory/harness-100 --skill branching-logic -a codex`. Or copy the skill folder (en/05-game-narrative/.claude/skills/branching-logic in revfactory/harness-100) into .agents/skills/branching-logic in your project. Codex loads it when a task matches its description.
Can I use Branching Logic 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 revfactory/harness-100 --skill branching-logic -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/branching-logic, .gemini/skills/branching-logic, .github/skills/branching-logic and .opencode/skills/branching-logic in your project.
What does Branching Logic need to run?
SKILL.md names no scripts, command-line tools or credentials: Branching Logic is instructions for the agent only.
Does Branching Logic 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 Branching Logic 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 Branching Logic use?
Branching Logic is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Branching Logic use?
About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Branching Logic?
Skills that share tags, products or a category with Branching Logic: 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 Pierre Theming Library (pierrecomputer/pierre, 6.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Branching Logic?
revfactory (a GitHub user) maintains it in revfactory/harness-100, which has 1,295 GitHub stars. The repository holds 464 skills in this directory. The repository was last updated on March 22, 2026.
Source: revfactory/harness-100 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.