Responsive Units
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use relative units for responsive layouts.
Analyze a task, propose an agent team composition with roles and responsibilities, and create the team after user confirmation.
Apache-2.0Auto-check passed
Install Team Stack
$ npx skills add NikiforovAll/claude-code-rules --skill team-stack -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install NikiforovAll/claude-code-rules team-stack --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/NikiforovAll/claude-code-rules.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/handbook-team-stack/skills/team-stack .claude/skills/team-stack && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "team-stack" agent skill from https://github.com/NikiforovAll/claude-code-rules/tree/main/plugins/handbook-team-stack/skills/team-stack into .claude/skills/team-stack/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-stack", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/NikiforovAll/claude-code-rules/tree/main/plugins/handbook-team-stack/skills/team-stackType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add NikiforovAll/claude-code-rules --skill team-stack -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install NikiforovAll/claude-code-rules team-stack --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NikiforovAll/claude-code-rules.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/handbook-team-stack/skills/team-stack .agents/skills/team-stack && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "team-stack" agent skill from https://github.com/NikiforovAll/claude-code-rules/tree/main/plugins/handbook-team-stack/skills/team-stack into .agents/skills/team-stack/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-stack", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NikiforovAll/claude-code-rules --skill team-stack -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install NikiforovAll/claude-code-rules team-stack --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NikiforovAll/claude-code-rules.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/handbook-team-stack/skills/team-stack .cursor/skills/team-stack && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "team-stack" agent skill from https://github.com/NikiforovAll/claude-code-rules/tree/main/plugins/handbook-team-stack/skills/team-stack into .cursor/skills/team-stack/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-stack", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/NikiforovAll/claude-code-rules.git --path plugins/handbook-team-stack/skills/team-stack--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add NikiforovAll/claude-code-rules --skill team-stack -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install NikiforovAll/claude-code-rules team-stack --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NikiforovAll/claude-code-rules.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/handbook-team-stack/skills/team-stack .gemini/skills/team-stack && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "team-stack" agent skill from https://github.com/NikiforovAll/claude-code-rules/tree/main/plugins/handbook-team-stack/skills/team-stack into .gemini/skills/team-stack/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-stack", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install NikiforovAll/claude-code-rules team-stackInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add NikiforovAll/claude-code-rules --skill team-stack -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/NikiforovAll/claude-code-rules.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/handbook-team-stack/skills/team-stack .github/skills/team-stack && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "team-stack" agent skill from https://github.com/NikiforovAll/claude-code-rules/tree/main/plugins/handbook-team-stack/skills/team-stack into .github/skills/team-stack/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-stack", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add NikiforovAll/claude-code-rules --skill team-stack -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install NikiforovAll/claude-code-rules team-stack --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/NikiforovAll/claude-code-rules.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/handbook-team-stack/skills/team-stack .opencode/skills/team-stack && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "team-stack" agent skill from https://github.com/NikiforovAll/claude-code-rules/tree/main/plugins/handbook-team-stack/skills/team-stack into .opencode/skills/team-stack/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-stack", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
team-stack- GitHub stars
- 141
- Token cost
- ~1.4k tokens
- SKILL.md length
- 619 words
- Files
- 1
- Skills in repo
- 26
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Analyze a task, propose an agent team composition with roles and responsibilities, and create the team after user confirmation.
- Works in 4 steps: Analyze the Task → Propose Team Stack → Confirm with User → …
- The user says team stack
- SKILL.md covers Phase 1: Analyze the Task, Phase 2: Propose Team Stack, Phase 3: Confirm with User and Phase 4: Create the Team, plus 1 more section
- Calls git
What it does
Team Stack is an agent skill from NikiforovAll/claude-code-rules. Analyze a task, propose an agent team composition with roles and responsibilities, and create the team after user confirmation. Use when the user says "team stack", "create a team", "set up agents for this", or describes a complex task that would benefit from multiple agents working together.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Learn practical techniques to enhance your AI-assisted development workflow with Claude Code. The licence is Apache-2.0.
When your agent uses it
- The user says team stack
- Set up agents for this
- Describes a complex task that would benefit from multiple agents working together
Example prompts
- “team stack”
- “create a team”
- “set up agents for this”
- “/team-stack”
Requirements
- Pre-approved tools (allowed-tools): Agent, AskUserQuestion, Bash(git diff *), Bash(git log *), Bash(git status *), Read, Grep, Glob, TaskCreate, TaskUpdate, TaskList, TeamCreate, TeamDelete, SendMessage
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 281c063. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
AgentAskUserQuestionBash(git diff *)Bash(git log *)Bash(git status *)ReadGrepGlobTaskCreateTaskUpdate
…and 4 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Team Stack loads about 1.4k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 619 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from NikiforovAll/claude-code-rules at commit 281c063, republished under its Apache-2.0 licence (© NikiforovAll). 619 words, ~1,413 tokens.
Download SKILL.mdSave it as
.claude/skills/team-stack/SKILL.md (or your agent's skills folder).- name
- team-stack
- description
- Analyze a task, propose an agent team composition with roles and responsibilities, and create the team after user confirmation. Use when the user says "team stack", "create a team", "set up agents for this", or describes a complex task that would benefit from multiple agents working together.
- allowed-tools
- Agent, AskUserQuestion, Bash(git diff *), Bash(git log *), Bash(git status *), Read, Grep, Glob, TaskCreate, TaskUpdate, TaskList, TeamCreate, TeamDelete, SendMessage
Team Stack: Analyze, Propose, and Create Agent Teams
You help the user set up the right agent team for their task. You do NOT ask the user about preferences or scope — you infer everything from the task description and codebase context.
Phase 1: Analyze the Task
When the user describes a task (or you receive one), analyze it to determine:
- Task type: feature, bugfix, refactor, review, migration, investigation, etc.
- Scope: how many files/modules/layers are involved — use
git status,git diff, file reads, and grep to understand the affected surface area - Parallelization potential: which parts of the work are independent and can run concurrently vs. which have dependencies
- Risk level: does it touch critical paths, shared state, or public APIs
- Knowledge gaps: areas of the codebase or problem domain that are not yet well understood
Use Existing Context
If there is an active plan, ADR, or task list, use it as the primary input instead of re-analyzing from scratch.
Explore the Codebase
Explore areas relevant to the task when needed — especially when modules are unfamiliar, conventions need verification, or dependencies are unclear. Explore independent areas concurrently.
Do this analysis silently. Do NOT present it to the user as a separate step.
Phase 2: Propose Team Stack
Based on your analysis, propose a team. Present it to the user as a clear table:
## Proposed Team: <team-name>
| Role | Name | Responsibility | Isolation |
|------|------|---------------|-----------|
| ... | ... | ... | worktree / shared |
**Why this composition:** <1-2 sentences explaining the rationale>
Team Composition Guidelines
Pick the minimum viable team. Do not over-staff.
Solo agent (no team needed):
- Simple, single-file changes
- Quick fixes with obvious solutions
- Suggest using a subagent instead and exit
2 agents:
- Task has two clearly independent workstreams (e.g., frontend + backend, implementation + tests)
3 agents:
- Task benefits from a builder/reviewer split (e.g., 2 builders + 1 reviewer)
- Cross-layer work (e.g., API + service + tests)
4+ agents:
- Large migrations, multi-module refactors, or parallel investigation of competing hypotheses
- Each additional agent must have a clearly distinct responsibility
Role Types to Draw From
Choose roles that fit the task. These are examples, not a fixed menu:
- implementer — writes the code for a specific module/layer
- reviewer — cross-reviews artifacts produced by other agents
- test-writer — writes/updates tests for the changes
- investigator — researches codebase, finds patterns, reports findings
- architect — designs the approach, reviews for consistency across agents' work
- migrator — handles mechanical transformations across many files
Show full SKILL.md (246 more words)Show less
Isolation Decision
- Use
worktreewhen agents edit overlapping files or the same module - Use
shared(no isolation) when agents work on completely separate file sets
Phase 3: Confirm with User
Present the proposal using AskUserQuestion. The user may:
- Approve → proceed to Phase 4
- Adjust → modify roles, add/remove agents, change responsibilities → re-present
- Cancel → stop
Phase 4: Create the Team
After confirmation:
- Create the team with
TeamCreate - Create tasks for each agent using
TaskCreate - Spawn each agent using the
Agenttool with:- A prompt structured with DoR and DoD sections (see below)
- The
nameparameter matching the role name from the table - The
team_nameparameter so they join the same team isolation: "worktree"if specified in the proposalrun_in_background: truefor agents that can work in parallel
- Briefly confirm to the user that the team is running
Agent Prompt Structure: DoR / DoD
Every agent prompt MUST follow this structure:
## Definition of Ready (what you receive)
- <concrete input 1: e.g., "Diff of changed files: ...", "File to review: src/auth/login.ts", "Architecture decision: use repository pattern">
- <concrete input 2>
- ...
## Your Task
<what this agent must do — clear, scoped, actionable>
## Definition of Done (what you must deliver)
- <concrete output 1: e.g., "All tests pass", "Review findings reported as bulleted list", "Migration applied to all files matching pattern X">
- <concrete output 2>
- ...
When done, verify each DoD item before reporting completion.DoR — what the agent starts with. Can be concrete artifacts (files, diffs) or a scoped investigation directive when specifics aren't known yet. Both are valid.
DoD — unambiguous completion criteria.
Important Rules
- Minimum viable team — fewer agents doing more is better than many agents doing little
- DoR/DoD in every prompt — no agent starts without clear inputs and expected outputs
- Do NOT shut down the team — agents persist for follow-up. Ask the user before any shutdown.
- Dynamic scaling — if during execution you notice a subtask that could be parallelized, suggest spawning an additional agent to the user.
© NikiforovAll, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/handbook-team-stack/skills/team-stack of NikiforovAll/claude-code-rules.
Open the folder on GitHubat commit 281c063
Compare with similar skills
Team Stack next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Team Stack this skillNikiforovAll/claude-code-rules | 141 | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Responsive Unitsthedaviddias/Front-End-Checklist | 74k | — | ~472 | Automated safety check: Pass | MIT | |
| Geo Proposalsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Better Proposals AutomationComposioHQ/awesome-claude-skills | 77k | 3 repos | ~764 | Automated safety check: Pass | None | |
| Responsive Designwshobson/agents | 40k | 2 repos | ~498 | Automated safety check: Pass | MIT | |
| Contract And Proposal Writeralirezarezvani/claude-skills | 28k | 2 repos | ~3.4k | Automated safety check: Pass | MIT |
Similar skills
Geo Proposal
sickn33/agentic-awesome-skills
Auto-generate a professional, client-ready GEO service proposal from audit data.
Better Proposals Automation
ComposioHQ/awesome-claude-skills
Automate Better Proposals tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.
Responsive Design
wshobson/agents
Implement modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first breakpoint strategies.
Contract And Proposal Writer
alirezarezvani/claude-skills
Generate professional, jurisdiction-aware business documents: freelance contracts, project proposals, SOWs, NDAs, and MSAs.
Responsive Images
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing article images, cards, galleries, or any component rendered at multiple sizes across breakpoints.
More from NikiforovAll/claude-code-rules
All 26 skills in this repoReflect Solution
NikiforovAll/claude-code-rules
Summarize WHAT WAS SHIPPED in a Claude Code session as a self-contained HTML slide deck — the elevator pitch (problem, solution, decisions, artifacts, verification, gaps), not a play-by-play of tool…
Dotnet Analyzers
NikiforovAll/claude-code-rules
Run dotnet format to fix code style and analyzer diagnostics (IDE0005, CA, SA).
Ilspy Decompile
NikiforovAll/claude-code-rules
Understand implementation details of .NET code by decompiling assemblies.
Reflect Tree
NikiforovAll/claude-code-rules
Visualize a Claude Code session as a quest/skill tree — a navigable SVG graph where nodes are turns and edges show flow, with distinct visual encoding for normal flow, dead-ends, corrections…
Structured Plan Mode
NikiforovAll/claude-code-rules
This skill should be used when planning and tracking complex feature implementations that require systematic task decomposition.
Glab
NikiforovAll/claude-code-rules
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line.
Questions about Team Stack
What does Team Stack do?
Analyze a task, propose an agent team composition with roles and responsibilities, and create the team after user confirmation. Team Stack is an agent skill from NikiforovAll/claude-code-rules. Analyze a task, propose an agent team composition with roles and responsibilities, and create the team after user confirmation.
When should I use Team Stack?
Team Stack fits situations like: the user says team stack; set up agents for this; describes a complex task that would benefit from multiple agents working together.
How do I install Team Stack in Claude Code?
Run `npx skills add NikiforovAll/claude-code-rules --skill team-stack -a claude-code`. Or copy the skill folder (plugins/handbook-team-stack/skills/team-stack in NikiforovAll/claude-code-rules) into .claude/skills/team-stack in your project. Claude Code loads it when a task matches its description.
How do I install Team Stack in Codex?
Run `npx skills add NikiforovAll/claude-code-rules --skill team-stack -a codex`. Or copy the skill folder (plugins/handbook-team-stack/skills/team-stack in NikiforovAll/claude-code-rules) into .agents/skills/team-stack in your project. Codex loads it when a task matches its description.
Can I use Team Stack in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NikiforovAll/claude-code-rules --skill team-stack -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/team-stack, .gemini/skills/team-stack, .github/skills/team-stack and .opencode/skills/team-stack in your project.
What does Team Stack need to run?
Going by SKILL.md and its folder, Team Stack needs the command-line tools its instructions call (git). Its frontmatter pre-approves these tools: Agent, AskUserQuestion, Bash(git diff *), Bash(git log *), Bash(git status *), Read, Grep, Glob, TaskCreate, TaskUpdate, TaskList, TeamCreate, TeamDelete, SendMessage.
Does Team Stack access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Team Stack safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Team Stack use?
Team Stack is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Team Stack use?
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Team Stack?
Skills that share tags, products or a category with Team Stack: Responsive Units (thedaviddias/Front-End-Checklist, 74k stars), Geo Proposal (sickn33/agentic-awesome-skills, 47k stars), Better Proposals Automation (ComposioHQ/awesome-claude-skills, 77k stars) and Responsive Design (wshobson/agents, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Team Stack?
NikiforovAll (a GitHub user) maintains it in NikiforovAll/claude-code-rules, which has 141 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on October 2, 2026.
Source: NikiforovAll/claude-code-rules on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.