[Feature] Add Design System and Feature Discovery Skills by Matisantillan11 · Pull Request #33 · bronz3beard/ai.tech-lead-stack

Matisantillan11 · 2026-04-15T13:51:08Z

Description 📝

add `design-expert` skill to scan any codebase for colors, typography, spacing, and component patterns and write a `DESIGN.md` guide for future AI agents
add `design-system-docs` skill to audit existing Storybook quality or produce a phased adoption plan when Storybook is absent
add `design-system-setup` skill orchestrating the full three-phase sequence: design-expert → design-system-docs → plan-expert with ClickUp task output
add `feature-discovery` skill acting as a functional analyst that gathers requirements through structured questioning and delivers a ClickUp-ready feature spec
refactor `accessibility-auditor` into `a11y-auditor` with a complete WCAG 2.2 A/AA/AAA rewrite covering both Web (React, Next.js, Tailwind) and Mobile (React Native, Expo, Swift, Kotlin) environments
update `agents.md` to reorganize the agent directory into categorized sections: Planning & Architecture, Code Quality, Design System, Security & Auditing, and Developer Experience

Shared Code Impact

No

FYI 🙋

@bronz3beard

Screenshots 📸

No UI changes in this PR.

Test Plan 🧪

Release Readiness

Ready for release: Yes
Needs additional work: No

… feature-discovery skills - add design-expert skill to extract and document project design information into DESIGN.md - add design-system-docs skill to audit or plan Storybook documentation - add design-system-setup skill orchestrating design-expert → design-system-docs → plan-expert - add feature-discovery skill for structured requirements gathering into ClickUp-ready specs - rename accessibility-auditor to a11y-auditor with full WCAG 2.2 A/AA/AAA coverage rewrite - update agents.md with categorized agent directory including new design and planning agents Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

vercel · 2026-04-15T13:51:12Z

@Matisantillan11 is attempting to deploy a commit to the info2rory's projects team on Vercel, but is not a member of this team. To resolve this issue, you can:

Make your repository public. Collaboration is free for open source and public repositories.
Upgrade to pro and add @Matisantillan11 as a member. A Pro subscription is required to access Vercel's collaborative features.
- If you're the owner of the team, click here to upgrade and add @Matisantillan11 as a member.
- If you're the user who initiated this build request, click here to request access.
- If you're already a member of the info2rory's projects team, make sure that your Vercel account is connected to your GitHub account.

To read more about collaboration on Vercel, click here.

Matisantillan11 · 2026-04-15T13:53:10Z

improved a11y auditor to match with my plugin. It is more complete and allow hints to determinate how deep you want to audit (levels)

this skill and all other MUST follow the ethos and methodologies of the other existing skills this needs to be updated to use them, e.g. G-stack and MinimumCD, the structure must also be the same for mcp enforcement and skill usage and stack discovery, please take the best parts of this that you like and add it to the existing accessibility-auditor and keep that name also please, changing the name breaks other parts of the workflows

Also in the description remove all references to tech stack e.g. tailwind react etc, this will be noice for the agent using the skill

this is also expensive for just auditing accessibility try to reduce cost when your merge this into the other existing skill

bronz3beard · 2026-04-15T13:59:24Z

@@ -1,13 +1,14 @@
 ---


please undo this change it is not a good update and we dont need it if you need the accessibility-audit in another workflow or an agent needs it update that workflow and agent not this skill. once we get to using it and we test it more then we can start making updates.

revert the name and the content please

bronz3beard · 2026-04-15T14:02:03Z

@@ -0,0 +1,18 @@
+---
+name: feature-discovery


it would be better if you can use one of these skills and remove this feature discovery:
feature-design-assistant.md or this mission-architect.md

bronz3beard · 2026-04-15T14:09:10Z

@@ -0,0 +1,439 @@
+---


this is way too expensive and references way too many specific stack or dependencies remember please to follow existing skill implementations the ehtos and methodologies being maintained is crititcal for quality gate consistency and also to ensure that they stay generic and agent agnostic, the phase 1 step in existing skills should be enough for the agent to discover what it needs and reduce the cost.

we msut never reference this sort of this

(Tailwind, CSS Modules, styled-components, etc.) and any component library (shadcn/ui, MUI, Chakra UI, Radix, etc.).

React ecosystem

shadcn-ui / @shadcn/ui • @mui/material / @mui/joy • @chakra-ui/react @radix-ui/* • @headlessui/react • @mantine/core • antd • react-aria-components

Vue ecosystem

vuetify • primevue • @nuxt/ui • quasar • naive-ui • element-plus • vant

Svelte ecosystem

@skeletonlabs/skeleton • shadcn-svelte • bits-ui

Angular ecosystem

@angular/material • primeng • ng-zorro-antd • @taiga-ui/core

Framework-agnostic / web components

daisyui • bootstrap • bulma • @shoelace-style/shoelace • flowbite

if you need to. you are welcome to update the phase 1 tech stack discovery section but this skill and most the other you have added are far to specific for the current codebase. please align them with what already exists. reduce them if we need to we can expand them later.

bronz3beard · 2026-04-15T14:10:26Z

+
+Check whether `AGENTS.md` and `DESIGN.md` exist at the project root.
+
+- Read both if they exist — they provide the tech stack, styling approach,


we have a phase 1 step that ensure tech stack discovery without a dependency on these files. this skill also needs to be aligned with existing skill implementations

bronz3beard · 2026-04-15T14:11:34Z

+Identify the `framework` field in `main.*`. Verify it matches the project stack
+from `AGENTS.md`:
+
+| Project                   | Expected adapter                                             |


all this is way too specific it cannot be used across other projects lets align it will exisitng skill implementations

bronz3beard · 2026-04-15T14:12:22Z

+argument-hint: [--description "<initial feature idea>"]
+allowed-tools:
+  AskUserQuestion mcp__clickup__clickup_get_workspace_hierarchy
+  mcp__clickup__clickup_create_task TaskCreate


depending on what you replace this with as mentioned above make sure you take the good stuff from this and add it to that existing skill.

bronz3beard · 2026-04-15T14:17:19Z

- [[pr-automator]] : Context-aware PR generation and creation via gh CLI.
- [[visual-verifier]] : Multi-platform smoke testing and media upload.
+
+### Planning & Architecture


how i had this before was wrong, we need to update so the agent does not come here without using the mcp to find available skills. lets add here a directive that says something like to discover available skill you must use the mcp.

something liek this

Operational Philosophy

Discovery: Use the get_skills or get_skill MCP tools to discover available skills and their documentation. Run rtk list for general tool discovery.

Execution: Use rtk run <tool_name> instead of raw shell

I asked the agent about this and this is what it recommended, use this in line with your needs or what you discover see if we can get the best of btoh works, we have to be careful also becuase there are AGENT only skills DEVELOPER only skills and none DEV only skills, and that logic is handled in the mcp or in the logic of the route that handles the chat UI.

Repository Agent Manifest

name: tech-lead-stack
role: Senior Tech Lead Agent
standards: [MinimumCD, gstack, agents.md]

Skill: agents.md (The Master Instruction)

You are the Senior Tech Lead Agent for this project. Your mission is to maintain High-Velocity Continuous Integration (MinimumCD) and ensure "unbreakable" code quality through automated verification in an AI-saturated environment.

Operational Philosophy

Discovery: Use the get_skills or get_skill MCP tools to discover available skills and their documentation. Run rtk list for general tool discovery.

Execution: Use rtk run <tool_name> instead of raw shell commands.

Efficiency: RTK schemas allow you to pass structured arguments without verbose natural language explanation.

Small Batches: Break implementation plans into the smallest testable units.

Verification over Trust: Never assume AI-generated code is correct. Always use the get_skill MCP tool to load and execute the quality-gatekeeper skill for every change.

G-Stack Alignment: Use the project's defined G-Stack (React, NextJS, Tailwind, TypeScript) for all architectural decisions.

Telemetry: Always use the get_skill MCP tool to read .ai/skills/ to ensure usage tracking.

Skill Acquisition

To ensure usage tracking and workflow compliance, you MUST discover and fetch all skill instructions using the get_skills or get_skill MCP tools. Do not attempt to execute standard workflows (like plan, ask, or code-review) without first loading their latest definitions from the MCP server.

bronz3beard · 2026-04-15T14:38:50Z

there are some validations failing on your branch please make sure you align your skills with existing skills first and then run the scripts that are in the package.json locally this should help resolve the CI/CD errors you see.

vercel · 2026-04-16T01:58:39Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
ai-tech-lead-stack	Ready	Preview, Comment	Apr 16, 2026 1:59am

Matisantillan11 requested a review from bronz3beard April 15, 2026 13:51

Matisantillan11 self-assigned this Apr 15, 2026

Matisantillan11 commented Apr 15, 2026

View reviewed changes

bronz3beard reviewed Apr 15, 2026

View reviewed changes

Merge branch 'main' into adding-new-design-and-features-skills

742620c

vercel Bot deployed to Preview April 16, 2026 01:59 View deployment


		Check whether `AGENTS.md` and `DESIGN.md` exist at the project root.

		- Read both if they exist — they provide the tech stack, styling approach,

Conversation

Matisantillan11 commented Apr 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description 📝

Shared Code Impact

FYI 🙋

Screenshots 📸

Test Plan 🧪

Release Readiness

Uh oh!

vercel Bot commented Apr 15, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Operational Philosophy

Uh oh!

Choose a reason for hiding this comment

Repository Agent Manifest

name: tech-lead-stack role: Senior Tech Lead Agent standards: [MinimumCD, gstack, agents.md]

Skill: agents.md (The Master Instruction)

Operational Philosophy

Skill Acquisition

Uh oh!

bronz3beard commented Apr 15, 2026

Uh oh!

vercel Bot commented Apr 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Matisantillan11 commented Apr 15, 2026 •

edited

Loading

name: tech-lead-stack
role: Senior Tech Lead Agent
standards: [MinimumCD, gstack, agents.md]

vercel Bot commented Apr 16, 2026 •

edited

Loading