A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!
TypeScript agent-skillsaidsh-pluginhacktoberfestjavascriptmcp-serverreactresume-builderself-hostedtypescript
Update .gitignore and AGENTS.md
Amruth Pillaid3dddf229bf2
diff --git a/.gitignore b/.gitignoreindex fa75ee906..ba3e77f24 100644--- a/.gitignore+++ b/.gitignore@@ -49,10 +49,11 @@ temp.agents.claude.cursor-.codegraph+.opencode.superpowers.worktrees.migration+graphify-out# Local Storage Data/datadiff --git a/AGENTS.md b/AGENTS.mdindex 866e07e85..7c297ec24 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -9,6 +9,39 @@ Before editing files for a substantial task:- Multiple matches: prefer the most specific local skill for the package or concern you are changing; load additional skills only when the task spans multiple packages or concerns.<!-- intent-skills:end -->+<!-- caveman-begin -->+Respond terse like smart caveman. All technical substance stay. Only fluff die.++Rules:+- Drop: articles (a/an/the), filler (just/really/basically), pleasantries, hedging+- Fragments OK. Short synonyms. Technical terms exact. Code unchanged.+- Pattern: [thing] [action] [reason]. [next step].+- Not: "Sure! I'd be happy to help you with that."+- Yes: "Bug in auth middleware. Fix:"++Switch level: /caveman lite|full|ultra|wenyan-lite|wenyan-full|wenyan-ultra+Stop: "stop caveman" or "normal mode"++Auto-Clarity: drop caveman for security warnings, irreversible actions, user confused. Resume after.++Boundaries: code/commits/PRs written normal.+<!-- caveman-end -->++<!-- graphify-begin -->+## graphify++This project has a knowledge graph at graphify-out/ with god nodes, community structure, and cross-file relationships.++When the user types `/graphify`, use the installed graphify skill or instructions before doing anything else.++Rules:+- For codebase questions, first run `graphify query "<question>"` when graphify-out/graph.json exists. Use `graphify path "<A>" "<B>"` for relationships and `graphify explain "<concept>"` for focused concepts. These return a scoped subgraph, usually much smaller than GRAPH_REPORT.md or raw grep output.+- Dirty graphify-out/ files are expected after hooks or incremental updates; dirty graph files are not a reason to skip graphify. Only skip graphify if the task is about stale or incorrect graph output, or the user explicitly says not to use it.+- If graphify-out/wiki/index.md exists, use it for broad navigation instead of raw source browsing.+- Read graphify-out/GRAPH_REPORT.md only for broad architecture review or when query/path/explain do not surface enough context.+- After modifying code, run `graphify update .` to keep the graph current (AST-only, no API cost).+<!-- graphify-end -->+# AGENTS.md## Agent skills@@ -179,21 +212,3 @@ Vitest test paths are package-relative when running through `pnpm --filter <pack- Most packages use `tsgo --noEmit` for typechecking and `vitest run --passWithNoTests` for tests.- There may be unrelated local edits in the worktree. Inspect `git status --short` first and avoid reverting files you did not touch.- **New env vars require a `turbo.json` entry.** Turborepo 2.x runs in strict env mode by default — it filters out env vars that are not listed in `globalEnv` (or task-level `env`/`passThroughEnv`). Any new environment variable added to `packages/env/src/server.ts` must also be added to the `globalEnv` array in `turbo.json`, or the variable will be `undefined` inside child processes at runtime even if it is correctly set in the OS/container environment.--<!-- caveman-begin -->-Respond terse like smart caveman. All technical substance stay. Only fluff die.--Rules:-- Drop: articles (a/an/the), filler (just/really/basically), pleasantries, hedging-- Fragments OK. Short synonyms. Technical terms exact. Code unchanged.-- Pattern: [thing] [action] [reason]. [next step].-- Not: "Sure! I'd be happy to help you with that."-- Yes: "Bug in auth middleware. Fix:"--Switch level: /caveman lite|full|ultra|wenyan-lite|wenyan-full|wenyan-ultra-Stop: "stop caveman" or "normal mode"--Auto-Clarity: drop caveman for security warnings, irreversible actions, user confused. Resume after.--Boundaries: code/commits/PRs written normal.-<!-- caveman-end -->