[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CTN8H1N39FCQ67AM7WD4S2":3,"skill-same:01M7CTN8H1N39FCQ67AM7WD4S2":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":46},"01M7CTN8H1N39FCQ67AM7WD4S2","init",null,"Set up a fresh repository, or adopt an existing one, to Lyngon conventions. Interviews the owner relentlessly about purpose, failure modes, audiences, stack and constraints, then writes INTENT.md, .claude\u002FCLAUDE.md, README.md, CONCEPTS.md, decision records, devenv, git hooks, CI and every package in the kind-first Lyngon layout. User-invoked only.","lyngon\u002Fdevkit","lyngon","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F70928830?v=4","01M7CTHVD57GT6VR6Y5SES6GKR","Lyngon","01M7CTHVDSGGTXSY9S7M5MA8RA",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flyngon\u002Fdevkit\u002Fblob\u002Fmain\u002Fplugins\u002Frepo\u002Fskills\u002Finit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: init\ndescription: Set up a fresh repository, or adopt an existing one, to Lyngon conventions. Interviews the owner relentlessly about purpose, failure modes, audiences, stack and constraints, then writes INTENT.md, .claude\u002FCLAUDE.md, README.md, CONCEPTS.md, decision records, devenv, git hooks, CI and every package in the kind-first Lyngon layout. User-invoked only.\ndisable-model-invocation: true\nargument-hint: \"[fresh|adopt]\"\n---\n\n# Initialize a repository\n\n## Overview\n\nOne session that takes a repository from \"empty\" or \"grown organically\" to the Lyngon baseline.\nThe interview is the core.\nThe files are its output, written only after the owner confirms a shared understanding.\n\nEvery repository this skill sets up has the Lyngon documents, the baseline and the workflow.\nThe one choice is the structure: the interview asks whether the repository adopts the layout defined in [STRUCTURE.md](STRUCTURE.md), and the structure files below are written only when it does.\nThe workflow comes with the settings, which enable `all` and each of its members: the standing instructions of `build` commit, push and open pull requests without asking.\n\n## When to use\n\n- The user asks to initialize, bootstrap, scaffold or set up a repository.\n- The user asks to adopt or bring an existing repository \"up to standard\".\n\n## When not to use\n\n- Adding a single file (a decision record, a hook) to a repository that already follows the baseline. Edit it directly.\n- Anything unrelated to repository structure. The skill does not write application code.\n\n## Workflow\n\nWork through the steps in order.\nDo not write files before step 3 is confirmed.\n\n### 1. Inventory\n\nFacts are your job, never the user's.\nBefore asking anything, look up:\n\n- `git remote -v`, `git log --oneline | head`, tracked files. No tracked files means **fresh** mode, otherwise **adopt** mode.\n- Existing `README.md`, `INTENT.md`, `CONCEPTS.md`, `CONTEXT.md`, `docs\u002Fdecisions\u002F`, `docs\u002FTODO.md`, and what an older setup left: a `CLAUDE.md` at the root or in a package, a line of `.claude\u002FCLAUDE.md` that is not an import, `AGENTS.md`, `docs\u002Fadr\u002F`.\n- Existing `devenv.nix`, `devenv.yaml`, `.envrc`, `flake.nix`, `.gitignore`, `.pre-commit-config.yaml`, `.claude\u002Fsettings.json`, `.mcp.json`, CI workflows.\n- Stack markers: `pyproject.toml`, `uv.lock`, `package.json`, `pnpm-lock.yaml`, `Cargo.toml`, `go.mod`, `*.tf`, `*.cabal`, `stack.yaml`, `*.nix`, shell scripts.\n- Existing package layout (`apps\u002F`, `libs\u002F`, a flat `packages\u002F`, `services\u002F`, per-language roots) and root workspace files (`pyproject.toml`, `pnpm-workspace.yaml`, `Cargo.toml`, `go.work`).\n- Existing tests and how they run.\n\nSummarize the inventory in at most ten lines, then start the interview.\nWhatever the inventory settled is not asked again.\n\n### 2. Interview\n\nInvoke two skills from the `discover` plugin: `discover:interview` for the rounds-and-frontier method, and `discover:domain-model` for settling terms into `CONCEPTS.md` and recording decisions.\nThen follow [references\u002Finterview.md](references\u002Finterview.md) for the question catalog, the first question (\"what would make this repository a failure in a year?\"), the rules specific to repository setup, and where each answer lands.\n\nEvery question carries a recommended answer.\nSkipped questions take the recommendation, and you say so at the start of the next round.\n\nDo not turn a \"don't know\" or \"later\" into a `docs\u002FTODO.md` item on your own.\nOnly what the user explicitly defers goes there.\n\nThe interview ends when the frontier is empty.\n\n### 3. Shared understanding\n\nPresent one table: every decision, its answer, and which file it lands in.\nList the decision records and the rule files you intend to write, by name.\nWait for the user to confirm.\nIf they change something, update the table and wait again.\n\n### 4. Plan the file set\n\nList every file you will create.\nIn adopt mode, show a diff for every file that already exists and never overwrite silently.\nFor `README.md` in adopt mode, merge into the existing structure rather than replacing it.\nIf an existing `README.md` states the problem, audience or non-goals, move that content into `INTENT.md` and leave a link behind.\n\nAn existing `CLAUDE.md` outside `.claude\u002F`, at the root or in a package, an `AGENTS.md`, a `docs\u002Fadr\u002F` and every line of an agent file that is not an import are sorted and then deleted, never kept.\nSort each line and each record by the admission test in `discover:domain-model`: drop what a check carries, what the tree shows and what holds for every Lyngon repository; a principle that passes becomes a rule file under `.claude\u002Frules\u002F`, with `paths:` when it concerns one package, and a decision that passes becomes a record under `docs\u002Fdecisions\u002F`, named after the decision.\nShow the owner the sorting before deleting anything.\nWhat the owner wants kept as it is goes into a rule file under `.claude\u002Frules\u002F`, never into an agent file: an agent file holds only imports.\n\n### 5. Write\n\nIn adopt mode, when the repository is on its default branch, create the branch first: `git switch -c chore\u002Fadopt-lyngon-conventions`.\n\nUse the templates and rules in [references\u002Frepo-files.md](references\u002Frepo-files.md) and [references\u002Fdevenv.md](references\u002Fdevenv.md).\nThe full set:\n\nThe documents:\n\n- `INTENT.md` from the round 1 answers: product, for whom, done, failure, non-goals, horizon.\n- `.claude\u002FCLAUDE.md` holding only the line that imports `INTENT.md`.\n- `\u003Cpackage>\u002F.claude\u002FCLAUDE.md` holding only the line `@..\u002FINTENT.md`, for each existing package with an `INTENT.md` of its own.\n- `.claude\u002Frules\u002F\u003Cname>.md` for each repository principle from step 3, one per file. Most repositories start with none.\n- `README.md`, `CONCEPTS.md`, `docs\u002Fdecisions\u002F\u003Cname>.md` for each decision record from step 3, `docs\u002FTODO.md` only if the user deferred something, `docs\u002Fconventions\u002F\u003Ctopic>.md` only for a repository-specific convention too long for a rule file.\n- `.gitignore` with the baseline patterns, `\u002Ftmp\u002F`, `\u002Fsandbox\u002F`, and the stack patterns.\n- `.claude\u002Fsettings.json` hiding the agent's commit attribution, registering the `lyngon` marketplace and enabling `all@lyngon` and each of its members by name. The README installs the bundle.\n- `.github\u002Fworkflows\u002Fci.yml` and `.github\u002Fworkflows\u002Fpull-request.yml` (or the equivalents for the chosen host).\n\nThe baseline:\n\n- `devenv.yaml`, `devenv.nix`, `.envrc`, `.vscode\u002Fextensions.json`.\n- `ruff.toml` and `[tool.basedpyright]` in the root `pyproject.toml` when Python is in the stack.\n- `tsconfig.base.json`, `eslint.config.js`, and their dev dependencies in the root `package.json`, when TypeScript is in the stack.\n- `secretspec.toml` and the `secretspec` section in `devenv.yaml` when the repository needs secrets.\n- Services (`services.*` in devenv) only when the user confirmed each one by name.\n\nThe structure, only when the repository adopts it:\n\n- `lyngon.structure.enable = true;` on a line of its own in the root `devenv.nix`; the session hook and `add-package` look for that line.\n- The root workspace file for every language in use, with explicit members (see `add-package`'s `workspaces.md` reference), and `languages.*` in the root `devenv.nix`.\n- Every package named in the interview, created through the `add-package` skill of this plugin, which puts it in the directory its kind decides, writes its files and registers it in its workspace and the root `devenv.yaml`.\n\n### 6. Verify\n\nRun, and fix what fails without disabling hooks:\n\n```sh\ndevenv test\n```\n\nAlso confirm that `git status` shows exactly the planned files.\nReport the result faithfully, including hooks that could not run.\n\n### 7. Commit and hand off\n\n`add-package` does not commit when this skill invokes it; the commits below include its packages.\n\nIn fresh mode the repository has no commits, so there is no base for a pull request: everything lands in one root commit on `main`.\n\n```sh\ngit symbolic-ref HEAD refs\u002Fheads\u002Fmain\ngit add -A\ngit commit -m \"chore: initialize repository\"\n```\n\nThe first command names the unborn branch `main` when git's default named it otherwise.\nAsk before pushing: the commit is on the default branch.\n\nIn adopt mode the work is on the branch step 5 created, or on the feature branch init started on.\nCommit by concern, in an order in which each commit passes the hooks, and put two concerns in one commit when neither passes alone:\n\n1. `docs: adopt the Lyngon documents`: `INTENT.md`, the agent files, the rule files, `README.md`, `CONCEPTS.md`, the decision records, `docs\u002F`, `.gitignore` and `.claude\u002Fsettings.json`, together with the removal of an old `CLAUDE.md`, `AGENTS.md` and `docs\u002Fadr\u002F`.\n2. `build: import the Lyngon baseline`: the devenv files, the linter configurations and `secretspec.toml`.\n3. `ci: run the full check and the pull request check in CI`: both workflows.\n4. `build: adopt the Lyngon structure`, only when the repository adopts it: the root workspace files; then one `feat(\u003Cname>): add \u003Ckind> \u003Cname>` per package.\n\nThen hand the branch over with `build:pull-request`.\n\nPrint the next steps for the owner:\n\n1. `devenv allow` in the repository.\n2. Either `direnv allow`, or `eval \"$(devenv hook zsh)\"` (or the equivalent for their shell) in their shell configuration.\n3. Install the VS Code extension `mkhl.direnv` so the Claude Code extension sees the devenv tools.\n4. In fresh mode without a remote: add one and push `main`.\n","# Initialize a repository\n\n## Overview\n\nOne session that takes a repository from \"empty\" or \"grown organically\" to the Lyngon baseline.\nThe interview is the core.\nThe files are its output, written only after the owner confirms a shared understanding.\n\nEvery repository this skill sets up has the Lyngon documents, the baseline and the workflow.\nThe one choice is the structure: the interview asks whether the repository adopts the layout defined in [STRUCTURE.md](STRUCTURE.md), and the structure files below are written only when it does.\nThe workflow comes with the settings, which enable `all` and each of its members: the standing instructions of `build` commit, push and open pull requests without asking.\n\n## When to use\n\n- The user asks to initialize, bootstrap, scaffold or set up a repository.\n- The user asks to adopt or bring an existing repository \"up to standard\".\n\n## When not to use\n\n- Adding a single file (a decision record, a hook) to a repository that already follows the baseline. Edit it directly.\n- Anything unrelated to repository structure. The skill does not write application code.\n\n## Workflow\n\nWork through the steps in order.\nDo not write files before step 3 is confirmed.\n\n### 1. Inventory\n\nFacts are your job, never the user's.\nBefore asking anything, look up:\n\n- `git remote -v`, `git log --oneline | head`, tracked files. No tracked files means **fresh** mode, otherwise **adopt** mode.\n- Existing `README.md`, `INTENT.md`, `CONCEPTS.md`, `CONTEXT.md`, `docs\u002Fdecisions\u002F`, `docs\u002FTODO.md`, and what an older setup left: a `CLAUDE.md` at the root or in a package, a line of `.claude\u002FCLAUDE.md` that is not an import, `AGENTS.md`, `docs\u002Fadr\u002F`.\n- Existing `devenv.nix`, `devenv.yaml`, `.envrc`, `flake.nix`, `.gitignore`, `.pre-commit-config.yaml`, `.claude\u002Fsettings.json`, `.mcp.json`, CI workflows.\n- Stack markers: `pyproject.toml`, `uv.lock`, `package.json`, `pnpm-lock.yaml`, `Cargo.toml`, `go.mod`, `*.tf`, `*.cabal`, `stack.yaml`, `*.nix`, shell scripts.\n- Existing package layout (`apps\u002F`, `libs\u002F`, a flat `packages\u002F`, `services\u002F`, per-language roots) and root workspace files (`pyproject.toml`, `pnpm-workspace.yaml`, `Cargo.toml`, `go.work`).\n- Existing tests and how they run.\n\nSummarize the inventory in at most ten lines, then start the interview.\nWhatever the inventory settled is not asked again.\n\n### 2. Interview\n\nInvoke two skills from the `discover` plugin: `discover:interview` for the rounds-and-frontier method, and `discover:domain-model` for settling terms into `CONCEPTS.md` and recording decisions.\nThen follow [references\u002Finterview.md](references\u002Finterview.md) for the question catalog, the first question (\"what would make this repository a failure in a year?\"), the rules specific to repository setup, and where each answer lands.\n\nEvery question carries a recommended answer.\nSkipped questions take the recommendation, and you say so at the start of the next round.\n\nDo not turn a \"don't know\" or \"later\" into a `docs\u002FTODO.md` item on your own.\nOnly what the user explicitly defers goes there.\n\nThe interview ends when the frontier is empty.\n\n### 3. Shared understanding\n\nPresent one table: every decision, its answer, and which file it lands in.\nList the decision records and the rule files you intend to write, by name.\nWait for the user to confirm.\nIf they change something, update the table and wait again.\n\n### 4. Plan the file set\n\nList every file you will create.\nIn adopt mode, show a diff for every file that already exists and never overwrite silently.\nFor `README.md` in adopt mode, merge into the existing structure rather than replacing it.\nIf an existing `README.md` states the problem, audience or non-goals, move that content into `INTENT.md` and leave a link behind.\n\nAn existing `CLAUDE.md` outside `.claude\u002F`, at the root or in a package, an `AGENTS.md`, a `docs\u002Fadr\u002F` and every line of an agent file that is not an import are sorted and then deleted, never kept.\nSort each line and each record by the admission test in `discover:domain-model`: drop what a check carries, what the tree shows and what holds for every Lyngon repository; a principle that passes becomes a rule file under `.claude\u002Frules\u002F`, with `paths:` when it concerns one package, and a decision that passes becomes a record under `docs\u002Fdecisions\u002F`, named after the decision.\nShow the owner the sorting before deleting anything.\nWhat the owner wants kept as it is goes into a rule file under `.claude\u002Frules\u002F`, never into an agent file: an agent file holds only imports.\n\n### 5. Write\n\nIn adopt mode, when the repository is on its default branch, create the branch first: `git switch -c chore\u002Fadopt-lyngon-conventions`.\n\nUse the templates and rules in [references\u002Frepo-files.md](references\u002Frepo-files.md) and [references\u002Fdevenv.md](references\u002Fdevenv.md).\nThe full set:\n\nThe documents:\n\n- `INTENT.md` from the round 1 answers: product, for whom, done, failure, non-goals, horizon.\n- `.claude\u002FCLAUDE.md` holding only the line that imports `INTENT.md`.\n- `\u003Cpackage>\u002F.claude\u002FCLAUDE.md` holding only the line `@..\u002FINTENT.md`, for each existing package with an `INTENT.md` of its own.\n- `.claude\u002Frules\u002F\u003Cname>.md` for each repository principle from step 3, one per file. Most repositories start with none.\n- `README.md`, `CONCEPTS.md`, `docs\u002Fdecisions\u002F\u003Cname>.md` for each decision record from step 3, `docs\u002FTODO.md` only if the user deferred something, `docs\u002Fconventions\u002F\u003Ctopic>.md` only for a repository-specific convention too long for a rule file.\n- `.gitignore` with the baseline patterns, `\u002Ftmp\u002F`, `\u002Fsandbox\u002F`, and the stack patterns.\n- `.claude\u002Fsettings.json` hiding the agent's commit attribution, registering the `lyngon` marketplace and enabling `all@lyngon` and each of its members by name. The README installs the bundle.\n- `.github\u002Fworkflows\u002Fci.yml` and `.github\u002Fworkflows\u002Fpull-request.yml` (or the equivalents for the chosen host).\n\nThe baseline:\n\n- `devenv.yaml`, `devenv.nix`, `.envrc`, `.vscode\u002Fextensions.json`.\n- `ruff.toml` and `[tool.basedpyright]` in the root `pyproject.toml` when Python is in the stack.\n- `tsconfig.base.json`, `eslint.config.js`, and their dev dependencies in the root `package.json`, when TypeScript is in the stack.\n- `secretspec.toml` and the `secretspec` section in `devenv.yaml` when the repository needs secrets.\n- Services (`services.*` in devenv) only when the user confirmed each one by name.\n\nThe structure, only when the repository adopts it:\n\n- `lyngon.structure.enable = true;` on a line of its own in the root `devenv.nix`; the session hook and `add-package` look for that line.\n- The root workspace file for every language in use, with explicit members (see `add-package`'s `workspaces.md` reference), and `languages.*` in the root `devenv.nix`.\n- Every package named in the interview, created through the `add-package` skill of this plugin, which puts it in the directory its kind decides, writes its files and registers it in its workspace and the root `devenv.yaml`.\n\n### 6. Verify\n\nRun, and fix what fails without disabling hooks:\n\n```sh\ndevenv test\n```\n\nAlso confirm that `git status` shows exactly the planned files.\nReport the result faithfully, including hooks that could not run.\n\n### 7. Commit and hand off\n\n`add-package` does not commit when this skill invokes it; the commits below include its packages.\n\nIn fresh mode the repository has no commits, so there is no base for a pull request: everything lands in one root commit on `main`.\n\n```sh\ngit symbolic-ref HEAD refs\u002Fheads\u002Fmain\ngit add -A\ngit commit -m \"chore: initialize repository\"\n```\n\nThe first command names the unborn branch `main` when git's default named it otherwise.\nAsk before pushing: the commit is on the default branch.\n\nIn adopt mode the work is on the branch step 5 created, or on the feature branch init started on.\nCommit by concern, in an order in which each commit passes the hooks, and put two concerns in one commit when neither passes alone:\n\n1. `docs: adopt the Lyngon documents`: `INTENT.md`, the agent files, the rule files, `README.md`, `CONCEPTS.md`, the decision records, `docs\u002F`, `.gitignore` and `.claude\u002Fsettings.json`, together with the removal of an old `CLAUDE.md`, `AGENTS.md` and `docs\u002Fadr\u002F`.\n2. `build: import the Lyngon baseline`: the devenv files, the linter configurations and `secretspec.toml`.\n3. `ci: run the full check and the pull request check in CI`: both workflows.\n4. `build: adopt the Lyngon structure`, only when the repository adopts it: the root workspace files; then one `feat(\u003Cname>): add \u003Ckind> \u003Cname>` per package.\n\nThen hand the branch over with `build:pull-request`.\n\nPrint the next steps for the owner:\n\n1. `devenv allow` in the repository.\n2. Either `direnv allow`, or `eval \"$(devenv hook zsh)\"` (or the equivalent for their shell) in their shell configuration.\n3. Install the VS Code extension `mkhl.direnv` so the Claude Code extension sees the devenv tools.\n4. In fresh mode without a remote: add one and push `main`.\n",{"name":5,"description":7,"argument-hint":24,"disable-model-invocation":25},"[fresh|adopt]",true,"main","7d4c29d5ef25e4bff96b8ed951739cd04811984b","plugins\u002Frepo\u002Fskills\u002Finit","https:\u002F\u002Fgithub.com\u002Flyngon\u002Fdevkit","https:\u002F\u002Fwww.lyngon.com","https:\u002F\u002Fgithub.com\u002Flyngon","www.lyngon.com","2026-11-14 19:00:56",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":25},[36,39,42],{"tool":37,"command":38},"npx","npx skills add lyngon\u002Fdevkit --skill init",{"tool":40,"command":41},"bunx","bunx skills add lyngon\u002Fdevkit --skill init",{"tool":43,"command":44},"pnpm","pnpm dlx skills add lyngon\u002Fdevkit --skill init","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flyngon\u002Fdevkit\u002Fblob\u002Fmain\u002Fplugins\u002Frepo\u002Fskills\u002Finit\u002FSKILL.md",[47,53,57,61],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fdevenv.md","REFERENCE","参考文档",21344,"https:\u002F\u002Fgithub.com\u002Flyngon\u002Fdevkit\u002Fblob\u002Fmain\u002Fplugins\u002Frepo\u002Fskills\u002Finit\u002Freferences\u002Fdevenv.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Finterview.md",6654,"https:\u002F\u002Fgithub.com\u002Flyngon\u002Fdevkit\u002Fblob\u002Fmain\u002Fplugins\u002Frepo\u002Fskills\u002Finit\u002Freferences\u002Finterview.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Frepo-files.md",10763,"https:\u002F\u002Fgithub.com\u002Flyngon\u002Fdevkit\u002Fblob\u002Fmain\u002Fplugins\u002Frepo\u002Fskills\u002Finit\u002Freferences\u002Frepo-files.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"STRUCTURE.md",31,"https:\u002F\u002Fgithub.com\u002Flyngon\u002Fdevkit\u002Fblob\u002Fmain\u002Fplugins\u002Frepo\u002Fskills\u002Finit\u002FSTRUCTURE.md",[66,73,80,87,94,101],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7CTNRE8KXX2CG9Q2XYYBTDE","unslop","Remove AI writing patterns from prose and give it a voice. Use whenever writing or editing non-code text (docs, READMEs, decision records, posts, commit messages, PR descriptions), before handing it over, and on request: \"unslop\", \"humanize\", \"make this sound human\", \"clean up this writing\", \"edit for voice\", \"de-AI this text\".","https:\u002F\u002Fgithub.com\u002Flyngon\u002Fdevkit\u002Fblob\u002Fmain\u002Fplugins\u002Fwriting\u002Fskills\u002Funslop\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7CTNHG9ENS5D6GCA9283V08","technical","Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use before writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages, every time, however small the document.","https:\u002F\u002Fgithub.com\u002Flyngon\u002Fdevkit\u002Fblob\u002Fmain\u002Fplugins\u002Fwriting\u002Fskills\u002Ftechnical\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7CTND9T9J9P1TR6RRDVAXF4","simpler","Restate the last message in plain human language, with no jargon. Use when the reader did not follow the last message and says so: \"bro\", \"say that simpler\", \"in plain words\", \"no jargon\".","https:\u002F\u002Fgithub.com\u002Flyngon\u002Fdevkit\u002Fblob\u002Fmain\u002Fplugins\u002Fwriting\u002Fskills\u002Fsimpler\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7CTN36H4AR1GATK3KE5E85X","add-package","Create a package in a Lyngon repository in the directory its kind decides (apps\u002F, libs\u002F, contracts\u002F, tools\u002F, infra\u002F), with README.md, devenv.nix and the layer lint, and register it in its workspace and devenv. Use whenever a new app, service, CLI, library, adapter, contract, schema, tool, infra module or environment is needed, including when one feature needs several packages. Never create a package by hand.","https:\u002F\u002Fgithub.com\u002Flyngon\u002Fdevkit\u002Fblob\u002Fmain\u002Fplugins\u002Frepo\u002Fskills\u002Fadd-package\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7CTMZE95Q1FJWKJRB8WCX4E","index","The index of Lyngon's principles, one line per principle saying when it applies and what it demands, each with a file under references\u002F. Invoke before work that takes judgment, such as a design choice, a refactor, a bug fix, a test, a measurement, a script, a document or a question to the owner; then read the file of each principle that applies.","https:\u002F\u002Fgithub.com\u002Flyngon\u002Fdevkit\u002Fblob\u002Fmain\u002Fplugins\u002Fprinciples\u002Fskills\u002Findex\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M7CTMSPW65SH5CXM4RVT20PB","why","Investigate why code, a design or a decision is the way it is, and return a cited answer that separates what was found from what is inferred and what is unknown. Reads the decision records, git history, pull request bodies and reviews, and issues, and any other evidence source the session offers. Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds, and before changing code whose reason is not visible. For how the code behaves at runtime, use discover:how.","https:\u002F\u002Fgithub.com\u002Flyngon\u002Fdevkit\u002Fblob\u002Fmain\u002Fplugins\u002Fdiscover\u002Fskills\u002Fwhy\u002FSKILL.md",[],[]]