Neetx/eso-skills / skills/eso-routine-planner
eso-routine-planner
VerifiedCreates, updates, and optimizes ESO ROUTINE.md plans. Use for daily, weekly, event, cross-character, cross-farming, limited-time, casual, efficient, or extreme play routines.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.6 KB |
| references/aurbis-shared-contract.md | markdown | 7.2 KB |
| references/markdown-output-patterns.md | markdown | 1.6 KB |
| references/persistent-files.md | markdown | 3.9 KB |
| references/query-scope.md | markdown | 931 B |
references/persistent-files.md
View on GitHub# Persistent Player Files
Use this reference when creating or updating player-state data.
## Storage Modes
Choose the first mode that applies:
1. **Workspace Mode** — the host provides a writable workspace (coding agent, Claude Code, Cursor). Create or update the Markdown files at the paths below.
2. **Projects Mode** — the user is working inside a Claude Project. Use artifacts to hold the player files. Save critical state summaries (roster overview, character list, CP level, platform) to the project instructions so they persist across conversations. Never offer file downloads as the primary persistence method.
3. **Chat-State Mode** — no workspace and no project. Keep the data in the current chat as named state blocks. Do not offer downloads, attachments, or fake saved files. Remind the user that data will not survive past this conversation.
In all modes, the Markdown structure remains the canonical data format.
## Location
Persistent player files live outside `skills/`:
- `players/account/TEAM.md`
- `players/account/RESOURCES.md`
- `players/account/ROUTINE.md`
- `players/account/GUILD.md`
- `players/account/CREATORS.md`
- `players/account/RESEARCH.md`
- `players/characters/character-slug/CHARACTER.md`
- `players/characters/character-slug/BUILDS.md`
- `players/characters/character-slug/ACTION_PLAN.md`
These are the only player files Aurbis creates. Do not create guides, summaries, tutorials, reference documents, or any other file not listed above. All output that is not a player-state file belongs in the conversation response, not on disk.
## Chat-State Names
Use readable names instead of raw paths when working in Chat-State Mode:
| Workspace file | Chat-State name |
|---|---|
| `players/account/TEAM.md` | `Aurbis Account Roster State` |
| `players/account/RESOURCES.md` | `Aurbis Account Resources State` |
| `players/account/ROUTINE.md` | `Aurbis Routine State` |
| `players/account/GUILD.md` | `Aurbis Guild State` |
| `players/account/CREATORS.md` | `Aurbis Creator References State` |
| `players/account/RESEARCH.md` | `Aurbis Crafting Research State` |
| `players/characters/character-slug/CHARACTER.md` | `Aurbis Character State: character name` |
| `players/characters/character-slug/BUILDS.md` | `Aurbis Build Armory State: character name` |
| `players/characters/character-slug/ACTION_PLAN.md` | `Aurbis Character Action Plan State: character name` |
## File Ownership
- `eso-character-manager` owns `CHARACTER.md`.
- `eso-team-manager` owns `TEAM.md`.
- `eso-build-theorycrafting` owns `BUILDS.md`.
- `eso-action-plan-manager` owns `ACTION_PLAN.md`.
- `eso-resource-manager` owns `RESOURCES.md`.
- `eso-routine-planner` owns `ROUTINE.md`.
- `eso-guild-social-manager` owns `GUILD.md`.
- `eso-content-creator-social-manager` owns `CREATORS.md`.
- `eso-crafting-research-planner` owns `RESEARCH.md`.
## Update Discipline
### Workspace Mode
- When the user requests a build, plan, routine, or character setup AND provides enough context (class, CP, platform), create the relevant player files automatically as part of the response. Do not ask for permission — persistence is the purpose of Workspace Mode.
- Create only the files that directly serve the request. If the user asks for a build, create CHARACTER.md and BUILDS.md. If they also need a farming route or plan, create ACTION_PLAN.md. Do not create RESOURCES.md, ROUTINE.md, or other files the user did not mention or need.
- For quick lookups, lore questions, or generic mechanics questions, do not create any files.
### Projects Mode and Chat-State Mode
- Ask before creating artifacts or state blocks unless the user explicitly requested tracking, saving, updating, or planning.
- In Chat-State Mode, remind the user that data does not survive past the conversation.
### All Modes
- Preserve uncertain extracted values as `needs confirmation` instead of treating them as facts.
- Include `Last updated` and, when relevant, source date or patch/update context.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |