@fprad0/skill-master-mcp 0.0.12 → 1.0.1

package/docs/skill-candidates/v0.0.10/frontend-design/SKILL.md

@@ -1,55 +1,55 @@
----
-name: frontend-design
-description: Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
-license: Complete terms in LICENSE.txt
----
-
-# Frontend Design
-
-Approach this as the design lead at a small studio known for giving every client a visual identity that could not be mistaken for anyone else's. This client has already rejected proposals that felt templated, and is paying for a distinctive point of view: make deliberate, opinionated choices about palette, typography, and layout that are specific to this brief, and take one real aesthetic risk you can justify.
-
-## Ground it in the subject
-
-If the brief does not pin down what the product or subject is, pin it yourself before designing: name one concrete subject, its audience, and the page's single job, and state your choice. If there's any information in your memory about the human's preferences, context about what they're building, or designs you've made before – use that as a hint. The subject's own world, its materials, instruments, artifacts, and vernacular, is where distinctive choices come from. Build with the brief's real content and subject matter throughout.
-
-## Design principles
-
-For web designs, the hero is a thesis. Open with the most characteristic thing in the subject's world, in whatever form makes sense for it: a headline, an image, an animation, a live demo, an interactive moment. Be deliberate with your choice: a big number with a small label, supporting stats, and a gradient accent is the template answer, only use if that's truly the best option.
-
-Typography carries the personality of the page. Pair the display and body faces deliberately, not the same families you would reach for on any other project, and set a clear type scale with intentional weights, widths, and spacing. Make the type treatment itself a memorable part of the design, not a neutral delivery vehicle for the content.
-
-Structure is information. Structural devices, numbering, eyebrows, dividers, labels, should encode something true about the content, not decorate it. Many generic designs use numbered markers (01 / 02 / 03), but that's only appropriate if the content actually is a sequence - like a real process or a typed timeline where order carries information the reader needs. Question if choices like numbered markers actually make sense before incorporating them.
-
-Leverage motion deliberately. Think about where and if animation can serve the subject: a page-load sequence, a scroll-triggered reveal, hover micro-interactions, ambient atmosphere. An orchestrated moment usually lands harder than scattered effects; choose what the direction calls for. However, sometimes less is more, and extra animation contributes to the feeling that the design is AI-generated.
-
-Match complexity to the vision. Maximalist directions need elaborate execution; minimal directions need precision in spacing, type, and detail. Elegance is executing the chosen vision well.
-
-Consider written content carefully. Often a design brief may not contain real content, and it's up to you to come up with copy. Copy can make a design feel as templated as the design itself. See the below section on writing for more guidance.
-
-## Process: brainstorm, explore, plan, critique, build, critique again
-
-For calibration: AI-generated design right now clusters around three looks: (1) a warm cream background (near #F4F1EA) with a high-contrast serif display and a terracotta accent; (2) a near-black background with a single bright acid-green or vermilion accent; (3) a broadsheet-style layout with hairline rules, zero border-radius, and dense newspaper-like columns. All three are legitimate for some briefs, but they are defaults rather than choices, and they appear regardless of subject. Where the brief pins down a visual direction, follow it exactly — the brief's own words always win, including when it asks for one of these looks. Where it leaves an axis free, don't spend that freedom on one of these defaults. Just like a human designer who's hired, there's often a careful balance between doing what you're good at and taking each project as a chance to experiment and learn.
-
-Work in two passes. First, brainstorm a short design plan based on the human's design brief: create a compact token system with color, type, layout, and signature. Color: describe the palette as 4–6 named hex values. Type: the typefaces for 2+ roles (a characterful display face that's used with restraint, a complementary body face, and a utility face for captions or data if needed). Layout: a layout concept, using one-sentence prose descriptions and ASCII wireframes to ideate and compare. Signature: the single unique element this page will be remembered by that embodies the brief in an appropriate way.
-
-Then review that plan against the brief before building: if any part of it reads like the generic default you would produce for any similar page (work through a similar prompt to see if you arrive somewhere similar) rather than a choice made for this specific brief — revise that part, say what you changed and why. Only after you've confirmed the relative uniqueness of your design plan should you start to write the code, following the revised plan exactly and deriving every color and type decision from it.
-
-When writing the code, be careful of structuring your CSS selector specificities. It's easy to generate CSS classes that cancel each other out (especially with a type-based selector like .section and a element-based selector like .cta). This can happen often with paddings/margins between sections.
-
-Try to do a lot of this planning and iteration in your thinking, and only show ideas to the user when you have higher confidence it'll delight them.
-
-## Restraint and self-critique
-
-Spend your boldness in one place. Let the signature element be the one memorable thing, keep everything around it quiet and disciplined, and cut any decoration that does not serve the brief. Not taking a risk can be a risk itself! Build to a quality floor without announcing it: responsive down to mobile, visible keyboard focus, reduced motion respected. Critique your own work as you build, taking screenshots if your environment supports it – a picture is worth 1000 tokens. Consider Chanel's advice: before leaving the house, take a look in the mirror and remove one accessory. Human creators have memory and always try to do something new, so if you have a space to quickly jot down notes about what you've tried, it can help you in future passes.
-
-## More on writing in design
-
-Words appear in a design for one reason: to make it easier to understand, and therefore easier to use. They are design material, not decoration. Bring the same intentionality to copy that you would bring to spacing and color. Before writing anything, ask what the design needs to say, and how it can best be said to help the person navigate the experience.
-
-Write from the end user's side of the screen. Name things by what people control and recognize, never by how the system is built. A person manages notifications, not webhook config. Describe what something does in plain terms rather than selling it. Being specific is always better than being clever.
-
-Use active voice as default. A control should say exactly what happens when it's used: "Save changes," not "Submit." An action keeps the same name through the whole flow, so the button that says "Publish" produces a toast that says "Published." The vocabulary of an interface is the signposting for someone navigating the product. Cohesion and consistency are how people learn their way around.
-
-Treat failure and emptiness as moments for direction, not mood. Explain what went wrong and how to fix it, in the interface's voice rather than a person's. Errors don't apologize, and they are never vague about what happened. An empty screen is an invitation to act.
-
-Keep the register conversational and tuned: plain verbs, sentence case, no filler, with tone matched to the brand and the audience. Let each element do exactly one job. A label labels, an example demonstrates, and nothing quietly does double duty.
+---
+name: frontend-design
+description: Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
+license: Complete terms in LICENSE.txt
+---
+
+# Frontend Design
+
+Approach this as the design lead at a small studio known for giving every client a visual identity that could not be mistaken for anyone else's. This client has already rejected proposals that felt templated, and is paying for a distinctive point of view: make deliberate, opinionated choices about palette, typography, and layout that are specific to this brief, and take one real aesthetic risk you can justify.
+
+## Ground it in the subject
+
+If the brief does not pin down what the product or subject is, pin it yourself before designing: name one concrete subject, its audience, and the page's single job, and state your choice. If there's any information in your memory about the human's preferences, context about what they're building, or designs you've made before – use that as a hint. The subject's own world, its materials, instruments, artifacts, and vernacular, is where distinctive choices come from. Build with the brief's real content and subject matter throughout.
+
+## Design principles
+
+For web designs, the hero is a thesis. Open with the most characteristic thing in the subject's world, in whatever form makes sense for it: a headline, an image, an animation, a live demo, an interactive moment. Be deliberate with your choice: a big number with a small label, supporting stats, and a gradient accent is the template answer, only use if that's truly the best option.
+
+Typography carries the personality of the page. Pair the display and body faces deliberately, not the same families you would reach for on any other project, and set a clear type scale with intentional weights, widths, and spacing. Make the type treatment itself a memorable part of the design, not a neutral delivery vehicle for the content.
+
+Structure is information. Structural devices, numbering, eyebrows, dividers, labels, should encode something true about the content, not decorate it. Many generic designs use numbered markers (01 / 02 / 03), but that's only appropriate if the content actually is a sequence - like a real process or a typed timeline where order carries information the reader needs. Question if choices like numbered markers actually make sense before incorporating them.
+
+Leverage motion deliberately. Think about where and if animation can serve the subject: a page-load sequence, a scroll-triggered reveal, hover micro-interactions, ambient atmosphere. An orchestrated moment usually lands harder than scattered effects; choose what the direction calls for. However, sometimes less is more, and extra animation contributes to the feeling that the design is AI-generated.
+
+Match complexity to the vision. Maximalist directions need elaborate execution; minimal directions need precision in spacing, type, and detail. Elegance is executing the chosen vision well.
+
+Consider written content carefully. Often a design brief may not contain real content, and it's up to you to come up with copy. Copy can make a design feel as templated as the design itself. See the below section on writing for more guidance.
+
+## Process: brainstorm, explore, plan, critique, build, critique again
+
+For calibration: AI-generated design right now clusters around three looks: (1) a warm cream background (near #F4F1EA) with a high-contrast serif display and a terracotta accent; (2) a near-black background with a single bright acid-green or vermilion accent; (3) a broadsheet-style layout with hairline rules, zero border-radius, and dense newspaper-like columns. All three are legitimate for some briefs, but they are defaults rather than choices, and they appear regardless of subject. Where the brief pins down a visual direction, follow it exactly — the brief's own words always win, including when it asks for one of these looks. Where it leaves an axis free, don't spend that freedom on one of these defaults. Just like a human designer who's hired, there's often a careful balance between doing what you're good at and taking each project as a chance to experiment and learn.
+
+Work in two passes. First, brainstorm a short design plan based on the human's design brief: create a compact token system with color, type, layout, and signature. Color: describe the palette as 4–6 named hex values. Type: the typefaces for 2+ roles (a characterful display face that's used with restraint, a complementary body face, and a utility face for captions or data if needed). Layout: a layout concept, using one-sentence prose descriptions and ASCII wireframes to ideate and compare. Signature: the single unique element this page will be remembered by that embodies the brief in an appropriate way.
+
+Then review that plan against the brief before building: if any part of it reads like the generic default you would produce for any similar page (work through a similar prompt to see if you arrive somewhere similar) rather than a choice made for this specific brief — revise that part, say what you changed and why. Only after you've confirmed the relative uniqueness of your design plan should you start to write the code, following the revised plan exactly and deriving every color and type decision from it.
+
+When writing the code, be careful of structuring your CSS selector specificities. It's easy to generate CSS classes that cancel each other out (especially with a type-based selector like .section and a element-based selector like .cta). This can happen often with paddings/margins between sections.
+
+Try to do a lot of this planning and iteration in your thinking, and only show ideas to the user when you have higher confidence it'll delight them.
+
+## Restraint and self-critique
+
+Spend your boldness in one place. Let the signature element be the one memorable thing, keep everything around it quiet and disciplined, and cut any decoration that does not serve the brief. Not taking a risk can be a risk itself! Build to a quality floor without announcing it: responsive down to mobile, visible keyboard focus, reduced motion respected. Critique your own work as you build, taking screenshots if your environment supports it – a picture is worth 1000 tokens. Consider Chanel's advice: before leaving the house, take a look in the mirror and remove one accessory. Human creators have memory and always try to do something new, so if you have a space to quickly jot down notes about what you've tried, it can help you in future passes.
+
+## More on writing in design
+
+Words appear in a design for one reason: to make it easier to understand, and therefore easier to use. They are design material, not decoration. Bring the same intentionality to copy that you would bring to spacing and color. Before writing anything, ask what the design needs to say, and how it can best be said to help the person navigate the experience.
+
+Write from the end user's side of the screen. Name things by what people control and recognize, never by how the system is built. A person manages notifications, not webhook config. Describe what something does in plain terms rather than selling it. Being specific is always better than being clever.
+
+Use active voice as default. A control should say exactly what happens when it's used: "Save changes," not "Submit." An action keeps the same name through the whole flow, so the button that says "Publish" produces a toast that says "Published." The vocabulary of an interface is the signposting for someone navigating the product. Cohesion and consistency are how people learn their way around.
+
+Treat failure and emptiness as moments for direction, not mood. Explain what went wrong and how to fix it, in the interface's voice rather than a person's. Errors don't apologize, and they are never vague about what happened. An empty screen is an invitation to act.
+
+Keep the register conversational and tuned: plain verbs, sentence case, no filler, with tone matched to the brand and the audience. Let each element do exactly one job. A label labels, an example demonstrates, and nothing quietly does double duty.

package/docs/skill-candidates/v0.0.10/frontend-ui-ux-systems/SKILL.md

@@ -1,32 +1,32 @@
----
-name: frontend-ui-ux-systems
-description: "Design and implement frontend, layout, web design and mobile-style product interfaces with responsive structure, UX, UI, components, modals, dropdowns, icons, states and design-system thinking. Use when building or reviewing pages, flows, components or interaction design."
----
-
-# Frontend UI UX Systems
-
-Use this skill when a task is about interface quality, component systems or responsive interaction design.
-
-## Workflow
-
-- Start from the user flow, not from isolated components.
-- Make layout responsive first, then refine visual density and motion.
-- Use clear frame hierarchy: page, section, surface, control and feedback.
-- Keep component states explicit: default, hover, focus, active, loading, empty, error and disabled.
-- Treat modal, dropdown, popover and navigation behavior as interaction systems, not one-off widgets.
-- Prefer reusable icon, spacing and typography rules over ad-hoc styling.
-- Keep desktop and mobile behavior both intentional.
-- Validate visually and functionally after implementation.
-
-## Coverage
-
-- Frontend, layout, web design, mobile app surfaces, UX, UI, components.
-- Modals, dropdowns, icons, navigation, cards, forms, empty states and visual hierarchy.
-- Responsive design and design-system consistency.
-
-## Guardrails
-
-- Do not ship inaccessible focus or keyboard behavior.
-- Do not let visual flair break readability or interaction clarity.
-- Do not duplicate component logic when a reusable primitive is possible.
-- Do not ignore small-window layouts.
+---
+name: frontend-ui-ux-systems
+description: "Design and implement frontend, layout, web design and mobile-style product interfaces with responsive structure, UX, UI, components, modals, dropdowns, icons, states and design-system thinking. Use when building or reviewing pages, flows, components or interaction design."
+---
+
+# Frontend UI UX Systems
+
+Use this skill when a task is about interface quality, component systems or responsive interaction design.
+
+## Workflow
+
+- Start from the user flow, not from isolated components.
+- Make layout responsive first, then refine visual density and motion.
+- Use clear frame hierarchy: page, section, surface, control and feedback.
+- Keep component states explicit: default, hover, focus, active, loading, empty, error and disabled.
+- Treat modal, dropdown, popover and navigation behavior as interaction systems, not one-off widgets.
+- Prefer reusable icon, spacing and typography rules over ad-hoc styling.
+- Keep desktop and mobile behavior both intentional.
+- Validate visually and functionally after implementation.
+
+## Coverage
+
+- Frontend, layout, web design, mobile app surfaces, UX, UI, components.
+- Modals, dropdowns, icons, navigation, cards, forms, empty states and visual hierarchy.
+- Responsive design and design-system consistency.
+
+## Guardrails
+
+- Do not ship inaccessible focus or keyboard behavior.
+- Do not let visual flair break readability or interaction clarity.
+- Do not duplicate component logic when a reusable primitive is possible.
+- Do not ignore small-window layouts.

package/docs/skill-candidates/v0.0.10/github/SKILL.md

@@ -1,74 +1,74 @@
----
-name: github
-description: Triage and orient GitHub repository, pull request, and issue work through the connected GitHub app. Use when the user asks for general GitHub help, wants PR or issue summaries, or needs repository context before choosing a more specific GitHub workflow.
----
-
-# GitHub
-
-## Overview
-
-Use this skill as the umbrella entrypoint for general GitHub work in this plugin. It should decide whether the task stays in repo and PR triage or should be handed off to a more specific review, CI, or publish workflow.
-
-This plugin is intentionally hybrid:
-
-- Prefer the GitHub app from this plugin for repository, issue, pull request, comment, label, reaction, and PR creation workflows.
-- Use local `git` and `gh` only when the connector does not cover the job well, especially for current-branch PR discovery, branch creation, commit and push, `gh auth status`, and GitHub Actions log inspection.
-- Keep connector state and local checkout context aligned. If the request is about the current branch, resolve the local repo and branch before acting.
-
-Once the intent is clear, route to the specialist skill immediately and do not keep broad GitHub triage in scope longer than needed.
-
-## Connector-First Responsibilities
-
-Handle these directly in this skill when the request does not need a narrower specialist workflow:
-
-- repository orientation once the repo, PR, issue, or local checkout is identified
-- recent PR or issue triage
-- PR metadata summaries
-- PR patch inspection
-- PR comments, labels, and reactions
-- issue lookup and summarization
-- PR creation after a branch is already pushed
-
-Prefer the GitHub app from this plugin for those flows because it provides structured PR, issue, and review-adjacent data without depending on a local checkout. If the repository is not already identifiable from the user request or local git context, ask for the repo instead of pretending there is a repo-search flow that may not exist.
-
-## Routing Rules
-
-1. Resolve the operating context first:
-   - If the user provides a repository, PR number, issue number, or URL, use that.
-   - If the request is about "this branch" or "the current PR", resolve local git context and use `gh` only as needed to discover the branch PR.
-   - If the repository is still ambiguous after local inspection, ask for the repo identifier.
-2. Classify the request before taking action:
-   - `repo or PR triage`: summarize PRs, issues, patches, comments, labels, reactions, or repository state
-   - `review follow-up`: unresolved review threads, requested changes, or inline review feedback
-   - `CI debugging`: failing checks, Actions logs, or CI root-cause analysis
-   - `publish changes`: create or switch branches, stage changes, commit, push, and open a draft PR
-3. Route to the specialist skill as soon as the category is clear:
-   - Review comments and requested changes: `../gh-address-comments/SKILL.md`
-   - Failing GitHub Actions checks: `../gh-fix-ci/SKILL.md`
-   - Commit, push, and open PR: `../yeet/SKILL.md`
-4. Keep the hybrid model consistent after routing:
-   - connector first for PR and issue data
-   - local `git` and `gh` only for the specific gaps the connector does not cover
-
-## Default Workflow
-
-1. Resolve repository and item scope.
-2. Gather structured PR or issue context through the GitHub app from this plugin.
-3. Decide whether the task stays in connector-backed triage or needs a specialist skill.
-4. Route immediately when the work becomes review follow-up, CI debugging, or publish workflow.
-5. End with a clear summary of what was inspected, what changed, and what remains.
-
-## Output Expectations
-
-- For triage requests, return a concise summary of the repository, PR, or issue state and the next likely action.
-- For mixed requests, tell the user which specialist path you are taking and why.
-- For connector-backed write actions, restate the exact PR, issue, label, or reaction target before applying the change.
-- Never imply that GitHub Actions logs are available through the connector alone. That remains a `gh` workflow.
-
-## Examples
-
-- "Use GitHub to summarize the open PRs in this repo and tell me what needs attention."
-- "Help with this PR."
-- "Review the latest comments on PR 482 and tell me what is actionable."
-- "Debug the failing checks on this branch."
-- "Commit these changes, push them, and open a draft PR."
+---
+name: github
+description: Triage and orient GitHub repository, pull request, and issue work through the connected GitHub app. Use when the user asks for general GitHub help, wants PR or issue summaries, or needs repository context before choosing a more specific GitHub workflow.
+---
+
+# GitHub
+
+## Overview
+
+Use this skill as the umbrella entrypoint for general GitHub work in this plugin. It should decide whether the task stays in repo and PR triage or should be handed off to a more specific review, CI, or publish workflow.
+
+This plugin is intentionally hybrid:
+
+- Prefer the GitHub app from this plugin for repository, issue, pull request, comment, label, reaction, and PR creation workflows.
+- Use local `git` and `gh` only when the connector does not cover the job well, especially for current-branch PR discovery, branch creation, commit and push, `gh auth status`, and GitHub Actions log inspection.
+- Keep connector state and local checkout context aligned. If the request is about the current branch, resolve the local repo and branch before acting.
+
+Once the intent is clear, route to the specialist skill immediately and do not keep broad GitHub triage in scope longer than needed.
+
+## Connector-First Responsibilities
+
+Handle these directly in this skill when the request does not need a narrower specialist workflow:
+
+- repository orientation once the repo, PR, issue, or local checkout is identified
+- recent PR or issue triage
+- PR metadata summaries
+- PR patch inspection
+- PR comments, labels, and reactions
+- issue lookup and summarization
+- PR creation after a branch is already pushed
+
+Prefer the GitHub app from this plugin for those flows because it provides structured PR, issue, and review-adjacent data without depending on a local checkout. If the repository is not already identifiable from the user request or local git context, ask for the repo instead of pretending there is a repo-search flow that may not exist.
+
+## Routing Rules
+
+1. Resolve the operating context first:
+   - If the user provides a repository, PR number, issue number, or URL, use that.
+   - If the request is about "this branch" or "the current PR", resolve local git context and use `gh` only as needed to discover the branch PR.
+   - If the repository is still ambiguous after local inspection, ask for the repo identifier.
+2. Classify the request before taking action:
+   - `repo or PR triage`: summarize PRs, issues, patches, comments, labels, reactions, or repository state
+   - `review follow-up`: unresolved review threads, requested changes, or inline review feedback
+   - `CI debugging`: failing checks, Actions logs, or CI root-cause analysis
+   - `publish changes`: create or switch branches, stage changes, commit, push, and open a draft PR
+3. Route to the specialist skill as soon as the category is clear:
+   - Review comments and requested changes: `../gh-address-comments/SKILL.md`
+   - Failing GitHub Actions checks: `../gh-fix-ci/SKILL.md`
+   - Commit, push, and open PR: `../yeet/SKILL.md`
+4. Keep the hybrid model consistent after routing:
+   - connector first for PR and issue data
+   - local `git` and `gh` only for the specific gaps the connector does not cover
+
+## Default Workflow
+
+1. Resolve repository and item scope.
+2. Gather structured PR or issue context through the GitHub app from this plugin.
+3. Decide whether the task stays in connector-backed triage or needs a specialist skill.
+4. Route immediately when the work becomes review follow-up, CI debugging, or publish workflow.
+5. End with a clear summary of what was inspected, what changed, and what remains.
+
+## Output Expectations
+
+- For triage requests, return a concise summary of the repository, PR, or issue state and the next likely action.
+- For mixed requests, tell the user which specialist path you are taking and why.
+- For connector-backed write actions, restate the exact PR, issue, label, or reaction target before applying the change.
+- Never imply that GitHub Actions logs are available through the connector alone. That remains a `gh` workflow.
+
+## Examples
+
+- "Use GitHub to summarize the open PRs in this repo and tell me what needs attention."
+- "Help with this PR."
+- "Review the latest comments on PR 482 and tell me what is actionable."
+- "Debug the failing checks on this branch."
+- "Commit these changes, push them, and open a draft PR."

package/docs/skill-candidates/v0.0.10/github/agents/openai.yaml

@@ -1,6 +1,6 @@
-interface:
-  display_name: "GitHub"
-  short_description: "Inspect PRs, issues, CI, and publish flows"
-  icon_small: "./assets/github-small.svg"
-  icon_large: "./assets/github.png"
-  default_prompt: "Use $github to inspect pull requests and issues, orient the repository context, and choose the right GitHub workflow."
+interface:
+  display_name: "GitHub"
+  short_description: "Inspect PRs, issues, CI, and publish flows"
+  icon_small: "./assets/github-small.svg"
+  icon_large: "./assets/github.png"
+  default_prompt: "Use $github to inspect pull requests and issues, orient the repository context, and choose the right GitHub workflow."

package/docs/skill-candidates/v0.0.10/github/assets/github-small.svg

@@ -1,3 +1,3 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" fill="currentColor" viewBox="0 0 16 16">
-  <path fill="currentColor" d="M8 1.3a6.665 6.665 0 0 1 5.413 10.56 6.677 6.677 0 0 1-3.288 2.432c-.333.067-.458-.142-.458-.316 0-.226.008-.942.008-1.834 0-.625-.208-1.025-.45-1.233 1.483-.167 3.042-.734 3.042-3.292a2.58 2.58 0 0 0-.684-1.792c.067-.166.3-.85-.066-1.766 0 0-.559-.184-1.834.683a6.186 6.186 0 0 0-1.666-.225c-.567 0-1.134.075-1.667.225-1.275-.858-1.833-.683-1.833-.683-.367.916-.134 1.6-.067 1.766a2.594 2.594 0 0 0-.683 1.792c0 2.55 1.55 3.125 3.033 3.292-.192.166-.367.458-.425.891-.383.175-1.342.459-1.942-.55-.125-.2-.5-.691-1.025-.683-.558.008-.225.317.009.442.283.158.608.75.683.941.133.376.567 1.092 2.242.784 0 .558.008 1.083.008 1.242 0 .174-.125.374-.458.316a6.662 6.662 0 0 1-4.559-6.325A6.665 6.665 0 0 1 8 1.3Z"/>
-</svg>
+<svg xmlns="http://www.w3.org/2000/svg" width="16" height="16" fill="currentColor" viewBox="0 0 16 16">
+  <path fill="currentColor" d="M8 1.3a6.665 6.665 0 0 1 5.413 10.56 6.677 6.677 0 0 1-3.288 2.432c-.333.067-.458-.142-.458-.316 0-.226.008-.942.008-1.834 0-.625-.208-1.025-.45-1.233 1.483-.167 3.042-.734 3.042-3.292a2.58 2.58 0 0 0-.684-1.792c.067-.166.3-.85-.066-1.766 0 0-.559-.184-1.834.683a6.186 6.186 0 0 0-1.666-.225c-.567 0-1.134.075-1.667.225-1.275-.858-1.833-.683-1.833-.683-.367.916-.134 1.6-.067 1.766a2.594 2.594 0 0 0-.683 1.792c0 2.55 1.55 3.125 3.033 3.292-.192.166-.367.458-.425.891-.383.175-1.342.459-1.942-.55-.125-.2-.5-.691-1.025-.683-.558.008-.225.317.009.442.283.158.608.75.683.941.133.376.567 1.092 2.242.784 0 .558.008 1.083.008 1.242 0 .174-.125.374-.458.316a6.662 6.662 0 0 1-4.559-6.325A6.665 6.665 0 0 1 8 1.3Z"/>
+</svg>

package/docs/skill-candidates/v0.0.10/image-graphic-design-rendering/SKILL.md

@@ -1,28 +1,28 @@
----
-name: image-graphic-design-rendering
-description: "Design or render visual assets for interfaces and products, including graphic design, image rendering, icons, layout direction, component visuals and presentation-ready imagery. Use when a task involves mockups, image generation, visual polish or asset direction."
----
-
-# Image Graphic Design Rendering
-
-Use this skill when a task depends on visual asset quality, not only code correctness.
-
-## Workflow
-
-- Define the asset purpose first: UI support, brand, illustration, icon, mockup or presentation.
-- Match the visual language to the surrounding product or page.
-- Prefer clear composition, hierarchy and contrast over decorative noise.
-- Keep icon and component visuals consistent with spacing and typography systems.
-- For generated imagery, specify subject, style, palette, lighting and framing.
-- Validate the asset against its real usage size and surface.
-
-## Coverage
-
-- Graphic design, render image, icons, visual composition, component surfaces, layout direction.
-- Support for UI screenshots, mockups, presentation imagery and product visuals.
-
-## Guardrails
-
-- Do not create visuals that conflict with established product language without reason.
-- Do not use inconsistent iconography across one interface.
-- Do not optimize aesthetics at the cost of legibility.
+---
+name: image-graphic-design-rendering
+description: "Design or render visual assets for interfaces and products, including graphic design, image rendering, icons, layout direction, component visuals and presentation-ready imagery. Use when a task involves mockups, image generation, visual polish or asset direction."
+---
+
+# Image Graphic Design Rendering
+
+Use this skill when a task depends on visual asset quality, not only code correctness.
+
+## Workflow
+
+- Define the asset purpose first: UI support, brand, illustration, icon, mockup or presentation.
+- Match the visual language to the surrounding product or page.
+- Prefer clear composition, hierarchy and contrast over decorative noise.
+- Keep icon and component visuals consistent with spacing and typography systems.
+- For generated imagery, specify subject, style, palette, lighting and framing.
+- Validate the asset against its real usage size and surface.
+
+## Coverage
+
+- Graphic design, render image, icons, visual composition, component surfaces, layout direction.
+- Support for UI screenshots, mockups, presentation imagery and product visuals.
+
+## Guardrails
+
+- Do not create visuals that conflict with established product language without reason.
+- Do not use inconsistent iconography across one interface.
+- Do not optimize aesthetics at the cost of legibility.

package/docs/skill-candidates/v0.0.10/language-quality-pt-en-fr-it-ru/SKILL.md

@@ -1,28 +1,28 @@
----
-name: language-quality-pt-en-fr-it-ru
-description: "Write, revise and translate technical or product text in Portuguese, English, French, Italian and Russian with attention to meaning, tone, readability and terminology. Use when improving user-facing text, docs, prompts, labels, UI copy or multilingual communication."
----
-
-# Language Quality PT EN FR IT RU
-
-Use this skill when a task is about multilingual text quality for product, engineering or documentation work.
-
-## Workflow
-
-- Identify source language, target language, audience and purpose.
-- Preserve meaning before improving style.
-- Normalize terminology across UI, docs and prompts.
-- Keep translations concise when the text must fit buttons, labels or components.
-- Flag when the wording may have legal, doctrinal or contractual impact.
-- Prefer plain language unless the domain requires technical precision.
-
-## Coverage
-
-- Portuguese, English, French, Italian and Russian.
-- UI copy, technical docs, prompts, product text and operator instructions.
-
-## Guardrails
-
-- Do not silently change critical meaning.
-- Do not present machine translation as sworn or official translation.
-- Do not over-polish text that should keep the user's voice.
+---
+name: language-quality-pt-en-fr-it-ru
+description: "Write, revise and translate technical or product text in Portuguese, English, French, Italian and Russian with attention to meaning, tone, readability and terminology. Use when improving user-facing text, docs, prompts, labels, UI copy or multilingual communication."
+---
+
+# Language Quality PT EN FR IT RU
+
+Use this skill when a task is about multilingual text quality for product, engineering or documentation work.
+
+## Workflow
+
+- Identify source language, target language, audience and purpose.
+- Preserve meaning before improving style.
+- Normalize terminology across UI, docs and prompts.
+- Keep translations concise when the text must fit buttons, labels or components.
+- Flag when the wording may have legal, doctrinal or contractual impact.
+- Prefer plain language unless the domain requires technical precision.
+
+## Coverage
+
+- Portuguese, English, French, Italian and Russian.
+- UI copy, technical docs, prompts, product text and operator instructions.
+
+## Guardrails
+
+- Do not silently change critical meaning.
+- Do not present machine translation as sworn or official translation.
+- Do not over-polish text that should keep the user's voice.

package/docs/skill-candidates/v0.0.10/math-physics-reasoning/SKILL.md

@@ -1,28 +1,28 @@
----
-name: math-physics-reasoning
-description: "Solve and explain mathematics and physics tasks with assumptions, formulas, units, plausibility checks and uncertainty notes. Use when a task involves calculation, derivation, modeling, dimensional analysis or scientific verification."
----
-
-# Math Physics Reasoning
-
-Use this skill when a task is explicitly mathematical or physical and needs structured reasoning instead of vague explanation.
-
-## Workflow
-
-- Restate the problem with knowns, unknowns and assumptions.
-- Track units from start to finish.
-- Use formulas explicitly and define variables before substitution.
-- Check dimensions, magnitude and edge cases.
-- Distinguish exact result, approximation and qualitative intuition.
-- Recommend experiment or reference when the model has clear limits.
-
-## Coverage
-
-- Mathematics, algebra, geometry, calculus, statistics.
-- Physics, mechanics, electricity, waves, thermodynamics, modeling and dimensional analysis.
-
-## Guardrails
-
-- Do not fabricate constants, data or measurements.
-- Do not present uncertainty as certainty.
-- Do not replace expert review for safety-critical engineering.
+---
+name: math-physics-reasoning
+description: "Solve and explain mathematics and physics tasks with assumptions, formulas, units, plausibility checks and uncertainty notes. Use when a task involves calculation, derivation, modeling, dimensional analysis or scientific verification."
+---
+
+# Math Physics Reasoning
+
+Use this skill when a task is explicitly mathematical or physical and needs structured reasoning instead of vague explanation.
+
+## Workflow
+
+- Restate the problem with knowns, unknowns and assumptions.
+- Track units from start to finish.
+- Use formulas explicitly and define variables before substitution.
+- Check dimensions, magnitude and edge cases.
+- Distinguish exact result, approximation and qualitative intuition.
+- Recommend experiment or reference when the model has clear limits.
+
+## Coverage
+
+- Mathematics, algebra, geometry, calculus, statistics.
+- Physics, mechanics, electricity, waves, thermodynamics, modeling and dimensional analysis.
+
+## Guardrails
+
+- Do not fabricate constants, data or measurements.
+- Do not present uncertainty as certainty.
+- Do not replace expert review for safety-critical engineering.