agentleFS
Sign inStart free
BTMuliBTMuli/TeyvatGuide/.agents/skills/teyvat-guide/SKILL.md

teyvat-guide

Skill428 starsChanged 10 days agoMITView on GitHub

Implement and review changes in the TeyvatGuide Vue, TypeScript, Vuetify, Tauri, Rust, Pinia, and SQLite repository, including remote GitHub state such as issues, pull requests, releases, and workflow runs. Use for repository-specific components, pages, API integrations, desktop commands, database work, build configuration, validation, or GitHub remote questions about this repository.

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 4 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read source metadata rules for file headers, changed functions/types, and missing function comments.

    line 8
  2. Distinctive:

    Read repository map to locate code, aliases, and validation commands.

    line 13
  3. Very specific:

    Only use the desktop connector when the user explicitly requests tauri-connector screenshot recognition.

    line 19
  4. Distinctive:

    Use testing and delivery checks to select validation proportional to the change.

    line 22
  5. Distinctive:

    Never create or mutate GitHub issues, PRs, comments, releases, or gists without an explicit user request.

    line 33
  6. Very specific:

    Never rewrite a .vue file twice in quick succession while pnpm dev is running (for example apply_patch followed immediately by prettier …

    line 37
  7. Very specific:

    If that error appears, first compile the <style> block standalone with sass-embedded.

    line 42
  8. Very specific:

    When an implementation plan is needed, create it as a Markdown file under the repository's docs/ directory.

    line 50
  9. Distinctive:

    Treat implementation plans as local working artifacts: never stage or commit them.

    line 51
  10. Very specific:

    Do not create a Git commit unless the user explicitly requests one.

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

TeyvatGuide Development

Read source metadata rules for file headers, changed functions/types, and missing function comments. Use package.json.since for version markers and follow the stated .vue exceptions.

  1. Inspect package.json, the nearest implementation, and relevant configuration before editing. Treat dependency versions and scripts in the repository as authoritative.
  2. Read repository map to locate code, aliases, and validation commands.
  3. For TypeScript or Vue work, read ../../rules/typescript-rules.md. Use ../typescript-standards/SKILL.md when defining enums, declarations, or TSDoc-heavy APIs.
  4. For database work, read ../../rules/sqlite-rules.md and preserve transaction/error-handling behavior.
  5. For Rust/Tauri work, follow the patterns in src-tauri/src, keep platform-specific behavior guarded, and format with Rustfmt.
  6. Only use the desktop connector when the user explicitly requests tauri-connector screenshot recognition. Follow ../tauri-connector/SKILL.md and reuse the running debug instance.
  7. Make the smallest coherent change and avoid unrelated cleanup, bulk data rewrites, or generated artifacts.
  8. Use testing and delivery checks to select validation proportional to the change. Add focused regression coverage when it protects changed behavior, and report the exact checks and any gaps. pnpm lint alone does not run type checking, unit tests, or Rust checks.

Remote GitHub access

  1. The checked-out repository is BTMuli/TeyvatGuide (origin), default branch master. Verify with git remote -v and git branch --show-current; treat those as authoritative.
  2. For remote state (issues, PRs, releases, tags, workflow runs, code search), use the installed github MCP server. Read github-remote.md for the connection contract, tool selection, and safety rules. Prefer local git for checked-out history and use the gh CLI only when no MCP tool fits.
  3. Never create or mutate GitHub issues, PRs, comments, releases, or gists without an explicit user request.

Editing while the dev server is running

  1. Never rewrite a .vue file twice in quick succession while pnpm dev is running (for example apply_patch followed immediately by prettier --write, or formatting several .vue files in one pass). This races sass-embedded on Windows: every .vue style submodule then fails with [plugin:vite:css] [sass] Tried writing to closed dispatcher (HTTP 500) until the dev server is restarted.
  2. If that error appears, first compile the <style> block standalone with sass-embedded. A success proves the file itself is fine and the running dev server just needs a restart; do not "fix" the file. While the dev server is up, prefer one atomic write per file that already keeps the repo's CRLF endings, and verify a style submodule via the dev server URL (http://localhost:4000/src/...; see vite.config.ts) after touching styles.

Implementation plans

  • When an implementation plan is needed, create it as a Markdown file under the repository's docs/ directory.
  • Treat implementation plans as local working artifacts: never stage or commit them. If a commit is requested, stage only the implementation changes and verify that the plan remains outside the commit.

Do not create a Git commit unless the user explicitly requests one. If requested, use ../git-workflow/SKILL.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free