{"owner":"johnpapa","repo":"angular-styleguide","hasSkills":true,"totalSkillsCount":2,"totalTokensCount":1437,"categories":["root-instruction","copilot-instructions"],"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md",".github/copilot-instructions.md"],"skills":{"AGENTS.md":"# Angular Style Guide — Agent Guide\n\n## Project Overview\n\n*Opinionated Angular style guide for teams by [John Papa](https://github.com/johnpapa).* This is the most widely adopted Angular style guide (26k+ stars), endorsed by the Angular team. It provides conventions for building Angular applications — syntax, structure, naming, and patterns — with *Why?* explanations for every recommendation.\n\nThis is a **documentation-only repository**. There is no source code, no build system, no test framework, and no runtime dependencies. The deliverables are markdown files.\n\n## Repository Structure\n\n```\nangular-styleguide/\n├── README.md              # Root — links to version-specific guides\n├── a1/                    # Angular 1 (AngularJS) style guide\n│   ├── README.md          # The full Angular 1 guide (~3,300 lines)\n│   ├── assets/            # Images, code snippets, editor templates\n│   └── i18n/              # Community translations (15+ languages)\n├── a2/                    # Angular 2+ style guide\n│   ├── README.md          # Angular 2 guide (references official docs)\n│   └── notes.md           # Development notes\n├── LICENSE                # MIT\n└── .github/               # GitHub configuration (AI-ready assets)\n```\n\n## Tech Stack\n\n- **Content format:** Markdown\n- **No runtime, build system, or test framework** — this is a documentation project\n\n## Build & Run\n\nThere is no build step. The content is read directly on GitHub or cloned locally. To preview markdown locally, use any markdown viewer or VS Code preview.\n\n## Testing\n\nThere are no automated tests. Validation is manual:\n- Read the markdown for accuracy and completeness\n- Verify code examples compile and follow the conventions they describe\n- Check that links are not broken\n\n## Key Patterns and Conventions\n\n- **The *Why?* pattern** — every rule has one or more `*Why?*:` bullets explaining the rationale\n- **Style IDs** — each rule has a unique ID (e.g., `[Style Y001]`) for easy reference\n- **Avoid / Recommended** — code examples show both the wrong way (`/* avoid */`) and the right way (`/* recommended */`)\n- **LIFT principle** — Locate, Identify, Flat, Try DRY (Y140-Y144)\n- **ATX headings** — `#`, `##`, `###` for structure\n- **Back to top links** — `**[Back to top](#table-of-contents)**` after each section\n\n## Adding a New Style Rule\n\n1. Choose the appropriate guide (`a1/README.md` for AngularJS, `a2/README.md` for Angular 2+)\n2. Assign a new Style ID following the numbering convention (e.g., `Y250` for the next in sequence)\n3. Write the rule with:\n   - A descriptive heading\n   - The style ID as a subheading: `###### [Style [Y250](#style-y250)]`\n   - One or more `*Why?*:` bullets\n   - `/* avoid */` and `/* recommended */` code examples\n4. Add a `**[Back to top](#table-of-contents)**` link at the end\n5. Add the rule to the Table of Contents at the top of the guide\n6. If the rule applies across languages, update translations in `a1/i18n/`\n\n## Documentation\n\nThis project **is** documentation. The guides live in:\n- `a1/README.md` — Angular 1 style guide (primary, most complete)\n- `a2/README.md` — Angular 2+ style guide (references official Angular docs)\n\nTranslations are maintained by the community in `a1/i18n/`.\n\n## Common Pitfalls\n\n- **Don't forget the Table of Contents** — every new rule must be added to the TOC at the top of the guide\n- **Translations go stale** — when updating `a1/README.md`, the 15+ translations in `a1/i18n/` may need updates. Flag this in the PR but don't auto-update translations.\n- **Code examples must be valid** — the `/* avoid */` and `/* recommended */` examples should be syntactically correct JavaScript/TypeScript\n- **Default branch is `master`** — not `main`\n",".github/copilot-instructions.md":"# Copilot Instructions — Angular Style Guide\n\n## Project Type\n\nThis is a **documentation-only repository** — markdown files containing style rules for Angular development. There is no source code to build or test.\n\n## Writing Conventions\n\n### The *Why?* Pattern\n\nEvery recommendation must include one or more `*Why?*:` bullets explaining the rationale. This is the signature pattern of the guide — never skip it.\n\n```markdown\n  *Why?*: One component per file promotes easier unit testing and mocking.\n\n  *Why?*: One component per file makes it far easier to read, maintain, and avoid collisions with teams in source control.\n```\n\n### Code Examples\n\nAlways show both the wrong way and the right way:\n\n```javascript\n  /* avoid */\n  // bad pattern here\n\n  /* recommended */\n  // good pattern here\n```\n\n### Style IDs\n\nEvery rule gets a unique ID in the format `[Style [Y###](#style-y###)]`. IDs are sequential within their category. When adding a new rule, use the next available number in the relevant section.\n\n### Formatting\n\n- Use ATX-style headings (`#`, `##`, `###`)\n- Indent code blocks with 2 spaces inside list items\n- End each section with `**[Back to top](#table-of-contents)**`\n- Use fenced code blocks with `javascript` or `html` language identifiers\n\n## Content Rules\n\n- **Be opinionated** — \"My recommended pattern is...\" not \"You might want to consider...\"\n- **Be specific** — real code, real patterns, real file names\n- **Keep rules focused** — one concept per rule, one purpose per section\n- **Explain tradeoffs** — when a rule has exceptions, note them\n\n## Maintenance Matrix\n\n| Change Made | Files to Update |\n|---|---|\n| New Angular 1 rule added | `a1/README.md` (rule + TOC entry) |\n| Existing rule modified | `a1/README.md`, flag translations in `a1/i18n/` for review |\n| New Angular 2+ rule added | `a2/README.md` |\n| Style ID numbering changed | Update all references in the TOC and cross-links |\n| New translation added | `a1/i18n/{locale}.md`, update root `README.md` if needed |\n| Assets added (images, snippets) | `a1/assets/`, reference from the relevant guide |\n"},"files":{"AGENTS.md":"# Angular Style Guide — Agent Guide\n\n## Project Overview\n\n*Opinionated Angular style guide for teams by [John Papa](https://github.com/johnpapa).* This is the most widely adopted Angular style guide (26k+ stars), endorsed by the Angular team. It provides conventions for building Angular applications — syntax, structure, naming, and patterns — with *Why?* explanations for every recommendation.\n\nThis is a **documentation-only repository**. There is no source code, no build system, no test framework, and no runtime dependencies. The deliverables are markdown files.\n\n## Repository Structure\n\n```\nangular-styleguide/\n├── README.md              # Root — links to version-specific guides\n├── a1/                    # Angular 1 (AngularJS) style guide\n│   ├── README.md          # The full Angular 1 guide (~3,300 lines)\n│   ├── assets/            # Images, code snippets, editor templates\n│   └── i18n/              # Community translations (15+ languages)\n├── a2/                    # Angular 2+ style guide\n│   ├── README.md          # Angular 2 guide (references official docs)\n│   └── notes.md           # Development notes\n├── LICENSE                # MIT\n└── .github/               # GitHub configuration (AI-ready assets)\n```\n\n## Tech Stack\n\n- **Content format:** Markdown\n- **No runtime, build system, or test framework** — this is a documentation project\n\n## Build & Run\n\nThere is no build step. The content is read directly on GitHub or cloned locally. To preview markdown locally, use any markdown viewer or VS Code preview.\n\n## Testing\n\nThere are no automated tests. Validation is manual:\n- Read the markdown for accuracy and completeness\n- Verify code examples compile and follow the conventions they describe\n- Check that links are not broken\n\n## Key Patterns and Conventions\n\n- **The *Why?* pattern** — every rule has one or more `*Why?*:` bullets explaining the rationale\n- **Style IDs** — each rule has a unique ID (e.g., `[Style Y001]`) for easy reference\n- **Avoid / Recommended** — code examples show both the wrong way (`/* avoid */`) and the right way (`/* recommended */`)\n- **LIFT principle** — Locate, Identify, Flat, Try DRY (Y140-Y144)\n- **ATX headings** — `#`, `##`, `###` for structure\n- **Back to top links** — `**[Back to top](#table-of-contents)**` after each section\n\n## Adding a New Style Rule\n\n1. Choose the appropriate guide (`a1/README.md` for AngularJS, `a2/README.md` for Angular 2+)\n2. Assign a new Style ID following the numbering convention (e.g., `Y250` for the next in sequence)\n3. Write the rule with:\n   - A descriptive heading\n   - The style ID as a subheading: `###### [Style [Y250](#style-y250)]`\n   - One or more `*Why?*:` bullets\n   - `/* avoid */` and `/* recommended */` code examples\n4. Add a `**[Back to top](#table-of-contents)**` link at the end\n5. Add the rule to the Table of Contents at the top of the guide\n6. If the rule applies across languages, update translations in `a1/i18n/`\n\n## Documentation\n\nThis project **is** documentation. The guides live in:\n- `a1/README.md` — Angular 1 style guide (primary, most complete)\n- `a2/README.md` — Angular 2+ style guide (references official Angular docs)\n\nTranslations are maintained by the community in `a1/i18n/`.\n\n## Common Pitfalls\n\n- **Don't forget the Table of Contents** — every new rule must be added to the TOC at the top of the guide\n- **Translations go stale** — when updating `a1/README.md`, the 15+ translations in `a1/i18n/` may need updates. Flag this in the PR but don't auto-update translations.\n- **Code examples must be valid** — the `/* avoid */` and `/* recommended */` examples should be syntactically correct JavaScript/TypeScript\n- **Default branch is `master`** — not `main`\n",".github/copilot-instructions.md":"# Copilot Instructions — Angular Style Guide\n\n## Project Type\n\nThis is a **documentation-only repository** — markdown files containing style rules for Angular development. There is no source code to build or test.\n\n## Writing Conventions\n\n### The *Why?* Pattern\n\nEvery recommendation must include one or more `*Why?*:` bullets explaining the rationale. This is the signature pattern of the guide — never skip it.\n\n```markdown\n  *Why?*: One component per file promotes easier unit testing and mocking.\n\n  *Why?*: One component per file makes it far easier to read, maintain, and avoid collisions with teams in source control.\n```\n\n### Code Examples\n\nAlways show both the wrong way and the right way:\n\n```javascript\n  /* avoid */\n  // bad pattern here\n\n  /* recommended */\n  // good pattern here\n```\n\n### Style IDs\n\nEvery rule gets a unique ID in the format `[Style [Y###](#style-y###)]`. IDs are sequential within their category. When adding a new rule, use the next available number in the relevant section.\n\n### Formatting\n\n- Use ATX-style headings (`#`, `##`, `###`)\n- Indent code blocks with 2 spaces inside list items\n- End each section with `**[Back to top](#table-of-contents)**`\n- Use fenced code blocks with `javascript` or `html` language identifiers\n\n## Content Rules\n\n- **Be opinionated** — \"My recommended pattern is...\" not \"You might want to consider...\"\n- **Be specific** — real code, real patterns, real file names\n- **Keep rules focused** — one concept per rule, one purpose per section\n- **Explain tradeoffs** — when a rule has exceptions, note them\n\n## Maintenance Matrix\n\n| Change Made | Files to Update |\n|---|---|\n| New Angular 1 rule added | `a1/README.md` (rule + TOC entry) |\n| Existing rule modified | `a1/README.md`, flag translations in `a1/i18n/` for review |\n| New Angular 2+ rule added | `a2/README.md` |\n| Style ID numbering changed | Update all references in the TOC and cross-links |\n| New translation added | `a1/i18n/{locale}.md`, update root `README.md` if needed |\n| Assets added (images, snippets) | `a1/assets/`, reference from the relevant guide |\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","rawUrl":"https://raw.githubusercontent.com/johnpapa/angular-styleguide/HEAD/AGENTS.md","title":"AI Agent Protocol & Instructions","category":"root-instruction","format":"markdown","content":"# Angular Style Guide — Agent Guide\n\n## Project Overview\n\n*Opinionated Angular style guide for teams by [John Papa](https://github.com/johnpapa).* This is the most widely adopted Angular style guide (26k+ stars), endorsed by the Angular team. It provides conventions for building Angular applications — syntax, structure, naming, and patterns — with *Why?* explanations for every recommendation.\n\nThis is a **documentation-only repository**. There is no source code, no build system, no test framework, and no runtime dependencies. The deliverables are markdown files.\n\n## Repository Structure\n\n```\nangular-styleguide/\n├── README.md              # Root — links to version-specific guides\n├── a1/                    # Angular 1 (AngularJS) style guide\n│   ├── README.md          # The full Angular 1 guide (~3,300 lines)\n│   ├── assets/            # Images, code snippets, editor templates\n│   └── i18n/              # Community translations (15+ languages)\n├── a2/                    # Angular 2+ style guide\n│   ├── README.md          # Angular 2 guide (references official docs)\n│   └── notes.md           # Development notes\n├── LICENSE                # MIT\n└── .github/               # GitHub configuration (AI-ready assets)\n```\n\n## Tech Stack\n\n- **Content format:** Markdown\n- **No runtime, build system, or test framework** — this is a documentation project\n\n## Build & Run\n\nThere is no build step. The content is read directly on GitHub or cloned locally. To preview markdown locally, use any markdown viewer or VS Code preview.\n\n## Testing\n\nThere are no automated tests. Validation is manual:\n- Read the markdown for accuracy and completeness\n- Verify code examples compile and follow the conventions they describe\n- Check that links are not broken\n\n## Key Patterns and Conventions\n\n- **The *Why?* pattern** — every rule has one or more `*Why?*:` bullets explaining the rationale\n- **Style IDs** — each rule has a unique ID (e.g., `[Style Y001]`) for easy reference\n- **Avoid / Recommended** — code examples show both the wrong way (`/* avoid */`) and the right way (`/* recommended */`)\n- **LIFT principle** — Locate, Identify, Flat, Try DRY (Y140-Y144)\n- **ATX headings** — `#`, `##`, `###` for structure\n- **Back to top links** — `**[Back to top](#table-of-contents)**` after each section\n\n## Adding a New Style Rule\n\n1. Choose the appropriate guide (`a1/README.md` for AngularJS, `a2/README.md` for Angular 2+)\n2. Assign a new Style ID following the numbering convention (e.g., `Y250` for the next in sequence)\n3. Write the rule with:\n   - A descriptive heading\n   - The style ID as a subheading: `###### [Style [Y250](#style-y250)]`\n   - One or more `*Why?*:` bullets\n   - `/* avoid */` and `/* recommended */` code examples\n4. Add a `**[Back to top](#table-of-contents)**` link at the end\n5. Add the rule to the Table of Contents at the top of the guide\n6. If the rule applies across languages, update translations in `a1/i18n/`\n\n## Documentation\n\nThis project **is** documentation. The guides live in:\n- `a1/README.md` — Angular 1 style guide (primary, most complete)\n- `a2/README.md` — Angular 2+ style guide (references official Angular docs)\n\nTranslations are maintained by the community in `a1/i18n/`.\n\n## Common Pitfalls\n\n- **Don't forget the Table of Contents** — every new rule must be added to the TOC at the top of the guide\n- **Translations go stale** — when updating `a1/README.md`, the 15+ translations in `a1/i18n/` may need updates. Flag this in the PR but don't auto-update translations.\n- **Code examples must be valid** — the `/* avoid */` and `/* recommended */` examples should be syntactically correct JavaScript/TypeScript\n- **Default branch is `master`** — not `main`\n","isInternal":false,"tokens":929,"sizeBytes":3809},{"name":"copilot-instructions.md","path":".github/copilot-instructions.md","rawUrl":"https://raw.githubusercontent.com/johnpapa/angular-styleguide/HEAD/.github/copilot-instructions.md","title":"GitHub Copilot Instructions","category":"copilot-instructions","format":"markdown","content":"# Copilot Instructions — Angular Style Guide\n\n## Project Type\n\nThis is a **documentation-only repository** — markdown files containing style rules for Angular development. There is no source code to build or test.\n\n## Writing Conventions\n\n### The *Why?* Pattern\n\nEvery recommendation must include one or more `*Why?*:` bullets explaining the rationale. This is the signature pattern of the guide — never skip it.\n\n```markdown\n  *Why?*: One component per file promotes easier unit testing and mocking.\n\n  *Why?*: One component per file makes it far easier to read, maintain, and avoid collisions with teams in source control.\n```\n\n### Code Examples\n\nAlways show both the wrong way and the right way:\n\n```javascript\n  /* avoid */\n  // bad pattern here\n\n  /* recommended */\n  // good pattern here\n```\n\n### Style IDs\n\nEvery rule gets a unique ID in the format `[Style [Y###](#style-y###)]`. IDs are sequential within their category. When adding a new rule, use the next available number in the relevant section.\n\n### Formatting\n\n- Use ATX-style headings (`#`, `##`, `###`)\n- Indent code blocks with 2 spaces inside list items\n- End each section with `**[Back to top](#table-of-contents)**`\n- Use fenced code blocks with `javascript` or `html` language identifiers\n\n## Content Rules\n\n- **Be opinionated** — \"My recommended pattern is...\" not \"You might want to consider...\"\n- **Be specific** — real code, real patterns, real file names\n- **Keep rules focused** — one concept per rule, one purpose per section\n- **Explain tradeoffs** — when a rule has exceptions, note them\n\n## Maintenance Matrix\n\n| Change Made | Files to Update |\n|---|---|\n| New Angular 1 rule added | `a1/README.md` (rule + TOC entry) |\n| Existing rule modified | `a1/README.md`, flag translations in `a1/i18n/` for review |\n| New Angular 2+ rule added | `a2/README.md` |\n| Style ID numbering changed | Update all references in the TOC and cross-links |\n| New translation added | `a1/i18n/{locale}.md`, update root `README.md` if needed |\n| Assets added (images, snippets) | `a1/assets/`, reference from the relevant guide |\n","isInternal":false,"tokens":508,"sizeBytes":2103}],"systemPromptSnippet":"<yakaai_skills repo=\"johnpapa/angular-styleguide\">\n<!-- File: AGENTS.md (Tokens: ~929 | Category: root-instruction) -->\n# Angular Style Guide — Agent Guide\n\n## Project Overview\n\n*Opinionated Angular style guide for teams by [John Papa](https://github.com/johnpapa).* This is the most widely adopted Angular style guide (26k+ stars), endorsed by the Angular team. It provides conventions for building Angular applications — syntax, structure, naming, and patterns — with *Why?* explanations for every recommendation.\n\nThis is a **documentation-only repository**. There is no source code, no build system, no test framework, and no runtime dependencies. The deliverables are markdown files.\n\n## Repository Structure\n\n```\nangular-styleguide/\n├── README.md              # Root — links to version-specific guides\n├── a1/                    # Angular 1 (AngularJS) style guide\n│   ├── README.md          # The full Angular 1 guide (~3,300 lines)\n│   ├── assets/            # Images, code snippets, editor templates\n│   └── i18n/              # Community translations (15+ languages)\n├── a2/                    # Angular 2+ style guide\n│   ├── README.md          # Angular 2 guide (references official docs)\n│   └── notes.md           # Development notes\n├── LICENSE                # MIT\n└── .github/               # GitHub configuration (AI-ready assets)\n```\n\n## Tech Stack\n\n- **Content format:** Markdown\n- **No runtime, build system, or test framework** — this is a documentation project\n\n## Build & Run\n\nThere is no build step. The content is read directly on GitHub or cloned locally. To preview markdown locally, use any markdown viewer or VS Code preview.\n\n## Testing\n\nThere are no automated tests. Validation is manual:\n- Read the markdown for accuracy and completeness\n- Verify code examples compile and follow the conventions they describe\n- Check that links are not broken\n\n## Key Patterns and Conventions\n\n- **The *Why?* pattern** — every rule has one or more `*Why?*:` bullets explaining the rationale\n- **Style IDs** — each rule has a unique ID (e.g., `[Style Y001]`) for easy reference\n- **Avoid / Recommended** — code examples show both the wrong way (`/* avoid */`) and the right way (`/* recommended */`)\n- **LIFT principle** — Locate, Identify, Flat, Try DRY (Y140-Y144)\n- **ATX headings** — `#`, `##`, `###` for structure\n- **Back to top links** — `**[Back to top](#table-of-contents)**` after each section\n\n## Adding a New Style Rule\n\n1. Choose the appropriate guide (`a1/README.md` for AngularJS, `a2/README.md` for Angular 2+)\n2. Assign a new Style ID following the numbering convention (e.g., `Y250` for the next in sequence)\n3. Write the rule with:\n   - A descriptive heading\n   - The style ID as a subheading: `###### [Style [Y250](#style-y250)]`\n   - One or more `*Why?*:` bullets\n   - `/* avoid */` and `/* recommended */` code examples\n4. Add a `**[Back to top](#table-of-contents)**` link at the end\n5. Add the rule to the Table of Contents at the top of the guide\n6. If the rule applies across languages, update translations in `a1/i18n/`\n\n## Documentation\n\nThis project **is** documentation. The guides live in:\n- `a1/README.md` — Angular 1 style guide (primary, most complete)\n- `a2/README.md` — Angular 2+ style guide (references official Angular docs)\n\nTranslations are maintained by the community in `a1/i18n/`.\n\n## Common Pitfalls\n\n- **Don't forget the Table of Contents** — every new rule must be added to the TOC at the top of the guide\n- **Translations go stale** — when updating `a1/README.md`, the 15+ translations in `a1/i18n/` may need updates. Flag this in the PR but don't auto-update translations.\n- **Code examples must be valid** — the `/* avoid */` and `/* recommended */` examples should be syntactically correct JavaScript/TypeScript\n- **Default branch is `master`** — not `main`\n\n<!-- File: .github/copilot-instructions.md (Tokens: ~508 | Category: copilot-instructions) -->\n# Copilot Instructions — Angular Style Guide\n\n## Project Type\n\nThis is a **documentation-only repository** — markdown files containing style rules for Angular development. There is no source code to build or test.\n\n## Writing Conventions\n\n### The *Why?* Pattern\n\nEvery recommendation must include one or more `*Why?*:` bullets explaining the rationale. This is the signature pattern of the guide — never skip it.\n\n```markdown\n  *Why?*: One component per file promotes easier unit testing and mocking.\n\n  *Why?*: One component per file makes it far easier to read, maintain, and avoid collisions with teams in source control.\n```\n\n### Code Examples\n\nAlways show both the wrong way and the right way:\n\n```javascript\n  /* avoid */\n  // bad pattern here\n\n  /* recommended */\n  // good pattern here\n```\n\n### Style IDs\n\nEvery rule gets a unique ID in the format `[Style [Y###](#style-y###)]`. IDs are sequential within their category. When adding a new rule, use the next available number in the relevant section.\n\n### Formatting\n\n- Use ATX-style headings (`#`, `##`, `###`)\n- Indent code blocks with 2 spaces inside list items\n- End each section with `**[Back to top](#table-of-contents)**`\n- Use fenced code blocks with `javascript` or `html` language identifiers\n\n## Content Rules\n\n- **Be opinionated** — \"My recommended pattern is...\" not \"You might want to consider...\"\n- **Be specific** — real code, real patterns, real file names\n- **Keep rules focused** — one concept per rule, one purpose per section\n- **Explain tradeoffs** — when a rule has exceptions, note them\n\n## Maintenance Matrix\n\n| Change Made | Files to Update |\n|---|---|\n| New Angular 1 rule added | `a1/README.md` (rule + TOC entry) |\n| Existing rule modified | `a1/README.md`, flag translations in `a1/i18n/` for review |\n| New Angular 2+ rule added | `a2/README.md` |\n| Style ID numbering changed | Update all references in the TOC and cross-links |\n| New translation added | `a1/i18n/{locale}.md`, update root `README.md` if needed |\n| Assets added (images, snippets) | `a1/assets/`, reference from the relevant guide |\n</yakaai_skills>"}