Results for “branching”

The craft of weaving story into interactive systems where the player is both audience and author. This skill covers the unique challenges of game narrative: branching structures that respect player agency, environmental storytelling that rewards exploration, dialogue systems that feel alive, and the delicate balance between authored experience and emergent narrative. Unlike linear media, games don't tell stories TO players - they create the conditions for stories to emerge WITH players. The narrative designer's job is to build the scaffolding that supports infinite player-authored moments while maintaining coherent themes and emotional arcs. This skill synthesizes lessons from Disco Elysium's internal monologue as gameplay, Hades' death-as-narrative-engine, interactive fiction's branching mastery (Inkle, Twine), and procedural narrative pioneers like Dwarf Fortress. It addresses ludonarrative harmony, bark systems, cinematics that respect agency, and the "and therefore" test that separates plot from story. Use when "narrative design, game story, game writing, dialogue system, branching narrative, player choice, environmental storytelling, bark system, quest design, lore delivery, ludonarrative, interactive fiction, inkle, twine, dialogue tree, player agency, cinematic design, voice direction, localization, procedural narrative, narrative, game-writing, dialogue, branching, player-agency, environmental-storytelling, quest-design, voice-acting, localization, interactive-fiction, procedural-narrative, ludonarrative" mentioned.

The English summary is being prepared. Showing the original description.

Operate and extend NanoClaw, an interactive command environment with sessions stored in Markdown. Resume, branch, search, compact, and export sessions, or switch models and load skills through slash commands.

• Resuming a saved NanoClaw session
• Branching a session before risky changes
• Searching across sessions and compacting history

Establish a Git workflow for team development, from choosing branches for separate changes to writing clear commits and pull requests. Includes history cleanup, merge versus rebase decisions, conflict resolution, and release tagging.

• Choosing a branching strategy for a new project
• Standardizing commit messages and pull request descriptions
• Tidying local commit history before a pull request

Manage Git branches, resolve conflicting changes, organize commit history, and recover earlier work after mistakes. Also helps teams choose a branching workflow that fits how they review changes, integrate work, and release software.

• Resolving conflicts during a merge or rebase
• Organizing commits before merging a branch
• Recovering deleted branches or older file versions

Expert patterns for Neon serverless Postgres, branching, connection pooling, and Prisma/Drizzle integrationUse when "neon database, serverless postgres, database branching, neon postgres, postgres serverless, connection pooling, preview environments, database per preview, neon, postgres, serverless, database, branching, prisma, drizzle, connection-pooling" mentioned.

The English summary is being prepared. Showing the original description.

Git is deceptively simple to learn and incredibly hard to master. The difference between a team that ships and a team that fights merge conflicts all day comes down to workflow discipline. Your git history is documentation - make it tell a story future you can understand. This skill covers branching strategies (trunk-based, gitflow, GitHub flow), commit hygiene, merge vs rebase, conflict resolution, and the commands you actually need. Key insight: most git disasters come from not understanding what you're about to do. 2025 lesson: Trunk-based development with short-lived branches has won. Long-lived feature branches are a code smell. If a branch lives more than a few days, something is wrong with your architecture or process. Use when "git workflow, branching strategy, git merge, git rebase, merge conflict, git commit, trunk-based, gitflow, git history, git revert, git reset, git, version-control, workflow, branching, commits, merge, rebase, collaboration" mentioned.

The English summary is being prepared. Showing the original description.

Git branching strategies, conflict resolution, rebase workflows, monorepo patterns, and advanced operations like cherry-pick, bisect, and reflog recovery. Activate on "git", "branching strategy", "merge conflict", "rebase", "cherry-pick", "monorepo git", "git bisect", "git reflog", "squash commits". NOT for GitHub Actions CI/CD (use github-actions-pipeline-builder), GitHub API/webhooks, or PR review processes (use code-review-checklist).

The English summary is being prepared. Showing the original description.

Analyze existing evolutionary trees and other hierarchical trees with ETE 4. Edit branches, add annotations, compare branching structures, explore large trees interactively, and render figures for publication using the appropriate optional visualization components.

• Prune selected species and change a tree's root
• Compare branching structures between two trees
• Add NCBI or GTDB taxonomy information

Set up Git workflows for Gitee, Coding.net, 极狐 GitLab, and CNB with platform-specific connection and authentication examples. Choose branching rules, standardize Chinese commit messages, and adapt automated testing and deployment configurations to your team's workflow.

• Configure connections and authentication for Chinese Git platforms
• Choose branching rules that fit the team
• Standardize Chinese commit messages and review templates

Helps users configure mirrord.json for database branching, enabling isolated database copies for safe development and testing. Use when the user wants to set up MySQL, MariaDB, PostgreSQL, MSSQL, MongoDB, Redis, DynamoDB, ClickHouse, Google Spanner, Amazon S3, turbopuffer, or generic branches, configure copy modes, connection sources, schema migrations, IAM authentication, or manage database branches.

The English summary is being prepared. Showing the original description.

Build branching dialogue and narrative — a node/choice graph with conditions, variables, and localization hooks — and choose between authoring tools Ink and Yarn Spinner or a custom data-driven runner. Engine-neutral. Use when the user mentions dialogue system, branching dialogue, conversation tree, choices, Ink (.ink), Yarn Spinner (.yarn), or NPC dialogue.

The English summary is being prepared. Showing the original description.

Build a visual novel: a branching script, character and background display, a text box with choices, save/load, backlog, and skip/auto. Use for a VN, dating sim, or branching story game.

The English summary is being prepared. Showing the original description.

Expert blueprint for quest tracking systems (objectives, progress, rewards, branching chains) using Resource-based quests, signal-driven updates, and AutoLoad managers. Use when implementing RPG quests or mission systems. Keywords quest, objectives, Quest Resource, QuestObjective, signal-driven, branching, rewards, AutoLoad.

The English summary is being prepared. Showing the original description.

Expert blueprint for visual novels (Doki Doki Literature Club, Phoenix Wright, Steins;Gate) focusing on branching narratives, dialogue systems, choice consequences, rollback mechanics, and persistent flags. Use when building story-driven, choice-based, or dating sim games. Keywords visual novel, dialogue system, branching narrative, typewriter effect, rollback, bbcode, RichTextLabel.

The English summary is being prepared. Showing the original description.

Expert patterns for branching dialogue systems including dialogue graphs (Resource-based), character portraits, player choices, conditional dialogue (flags/quests), typewriter effects, localization support, and voice acting integration. Use for narrative games, RPGs, or visual novels. Trigger keywords: DialogueLine, DialogueChoice, DialogueGraph, dialogue_manager, typewriter_effect, branching_dialogue, dialogue_flags, localization, voice_acting.

The English summary is being prepared. Showing the original description.

Expert blueprint for quest tracking systems (objectives, progress, rewards, branching chains) using Resource-based quests, signal-driven updates, and AutoLoad managers. Use when implementing RPG quests or mission systems. Keywords quest, objectives, Quest Resource, QuestObjective, signal-driven, branching, rewards, AutoLoad.

The English summary is being prepared. Showing the original description.

Expert blueprint for visual novels (Doki Doki Literature Club, Phoenix Wright, Steins;Gate) focusing on branching narratives, dialogue systems, choice consequences, rollback mechanics, and persistent flags. Use when building story-driven, choice-based, or dating sim games. Keywords visual novel, dialogue system, branching narrative, typewriter effect, rollback, bbcode, RichTextLabel.

The English summary is being prepared. Showing the original description.

Expert patterns for branching dialogue systems including dialogue graphs (Resource-based), character portraits, player choices, conditional dialogue (flags/quests), typewriter effects, localization support, and voice acting integration. Use for narrative games, RPGs, or visual novels. Trigger keywords: DialogueLine, DialogueChoice, DialogueGraph, dialogue_manager, typewriter_effect, branching_dialogue, dialogue_flags, localization, voice_acting.

The English summary is being prepared. Showing the original description.

Designs team Git workflows for branching, PRs, and releases. Use when choosing branching models, stacked PRs, merge queues, worktree isolation for agents, or collaboration rules.

The English summary is being prepared. Showing the original description.

Use this skill to gather, document, and validate OmniScript flow design requirements before development begins — covering screen layout requirements, branching logic, data source requirements, and user journey mapping. Trigger keywords: OmniScript requirements, OmniScript BA, OmniScript screen design, OmniScript user journey, OmniScript branching requirements. NOT for building the OmniScript or moving logic into an Integration Procedure — use omnistudio/omniscript-design-patterns. NOT for FlexCard requirements — use admin/flexcard-requirements.

The English summary is being prepared. Showing the original description.

Expert in Git workflows, conventions, and patterns for modern development teams and AI agents. Activate on: branching strategy, commit conventions, git hooks, pre-commit, husky, lint-staged, trunk-based development, git worktree, monorepo git, PR review workflow, conventional commits, git workflow. NOT for: CI/CD pipelines (use github-actions-pipeline-builder), repository hosting (use devops-automator), multi-agent orchestration (use multi-agent-coordination).

The English summary is being prepared. Showing the original description.

Expert patterns for Neon serverless Postgres, branching, connection pooling, and Prisma/Drizzle integration Use when: neon database, serverless postgres, database branching, neon postgres, postgres serverless.

The English summary is being prepared. Showing the original description.

Use Neon serverless Postgres with branching, connection pooling, and instant scalability for modern applications with Prisma or Drizzle ORM integration. Use when setting up serverless Postgres databases, implementing database branching for preview environments, configuring connection pooling, optimizing for serverless cold starts, using Prisma with Neon, implementing database migrations, scaling databases automatically, or building applications on Vercel/Netlify with Postgres.

The English summary is being prepared. Showing the original description.

Examine a plan, decision, or idea through structured rounds of questions with recommended answers. Organize dependent decisions into a branching map, resolve assumptions, and build a shared understanding before taking action.

• Stress-testing a plan before acting
• Clarifying assumptions behind an idea
• Sorting out dependent decisions