Repository for AI Team
$git clone https://github.com/dezkareid/ai-teamInstalls into the current project.
Install ai-team by running `git clone https://github.com/dezkareid/ai-team`, then use it for the current task and follow its documentation at https://github.com/dezkareid/ai-team.
| 1 | # ai-team |
| 2 | |
| 3 | Repository with AI tooling for teams — Gemini CLI extensions and Claude Code marketplace plugins. |
| 4 | |
| 5 | ## Gemini CLI |
| 6 | |
| 7 | ### Installation |
| 8 | |
| 9 | ```bash |
| 10 | gemini extensions install https://github.com/dezkareid/ai-team |
| 11 | ``` |
| 12 | |
| 13 | ## Claude Code |
| 14 | |
| 15 | ### Install the marketplace |
| 16 | |
| 17 | Add this marketplace to Claude Code so it can discover the available plugins: |
| 18 | |
| 19 | ```bash |
| 20 | claude marketplace add dezkareid-ai-team https://github.com/dezkareid/ai-team |
| 21 | ``` |
| 22 | |
| 23 | ### Available plugins |
| 24 | |
| 25 | #### `npm-tools` — Tools for working with npm |
| 26 | |
| 27 | | Command | Description | |
| 28 | |---|---| |
| 29 | | `npm-package-setup` | Initialize and publish a new npm package. | |
| 30 | | `npm-publish` | Setup NPM publication workflow with OIDC and provenance using local standard actions (Monorepo & pnpm support). | |
| 31 | |
| 32 | #### `design-system` — Authoritative design system context and tools |
| 33 | |
| 34 | | Skill | Description | |
| 35 | |---|---| |
| 36 | | `design-tokens` | Authoritative context for the project's design tokens. Provides information on colors, spacing, and breakpoints using CSS custom properties. | |
| 37 | |
| 38 | #### `company-context` — Authoritative company context and tools |
| 39 | |
| 40 | ### AI Team MCP |
| 41 | |
| 42 | The `ai-team` MCP server provides authoritative business and architectural context to AI agents. |
| 43 | |
| 44 | #### Available Tools |
| 45 | |
| 46 | | Tool | Description | |
| 47 | |---|---| |
| 48 | | `get_enterprise_context` | Retrieves the enterprise mission, strategic goals, and core architecture characteristics. | |
| 49 | | `get_company_outcomes` | Retrieves the high-level business outcomes and key results for the enterprise. | |
| 50 | | `get_architecture_principles` | Retrieves the technology-agnostic architecture principles and quality standards. | |
| 51 | | `search_product` | Searches for a specific product's characteristics and goals. Returns a default profile if not found. | |
| 52 | |
| 53 | #### Context Structure |
| 54 | |
| 55 | The documentation follows a hierarchical, technology-agnostic structure: |
| 56 | |
| 57 | ```text |
| 58 | context/ |
| 59 | ├── enterprise.md # Mission, goals, and core characteristics |
| 60 | ├── outcomes.md # Shared strategic outcomes (OKRs) |
| 61 | ├── architecture-principles.md # Fundamental philosophy and standards |
| 62 | └── products/ # Product-specific characteristics |
| 63 | ├── personal-website.md |
| 64 | ├── collecstory.md |
| 65 | └── default.md # Fallback for undocumented products |
| 66 | ``` |
| 67 | |
| 68 | #### `web-quality` — Skills for auditing and optimizing web quality |
| 69 | |
| 70 | | Skill | Description | |
| 71 | |---|---| |
| 72 | | `web-quality-audit` | Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. | |
| 73 | | `performance` | Optimize web performance for faster loading and better user experience. | |
| 74 | | `accessibility` | Audit and improve web accessibility following WCAG 2.2 guidelines. | |
| 75 | | `seo` | Optimize for search engine visibility and ranking. | |
| 76 | | `core-web-vitals` | Optimize Core Web Vitals (LCP, INP, CLS) for better page experience and search ranking. | |
| 77 | | `best-practices` | Apply modern web development best practices for security, compatibility, and code quality. | |
| 78 | |
| 79 | #### `frontend-tools` — Expert procedural guidance for frontend development |
| 80 | |
| 81 | | Skill | Description | |
| 82 | |---|---| |
| 83 | | `react-best-practices` | Expert guidance for React development, including hooks, performance, and patterns. | |
| 84 | | `next-best-practices` | Best practices for Next.js applications, including RSC, caching, and routing. | |
| 85 | |
| 86 | #### `database-tools` — Expert procedural guidance for database optimization and best practices |
| 87 | |
| 88 | | Skill | Description | |
| 89 | |---|---| |
| 90 | | `supabase-postgres-best-practices` | Postgres performance optimization and best practices from Supabase. | |
| 91 | |
| 92 | ### Install a plugin |
| 93 | |
| 94 | Once the marketplace is added, install a plugin with: |
| 95 | |
| 96 | ```bash |
| 97 | claude plugin install npm-tools |
| 98 | claude plugin install design-system |
| 99 | claude plugin install company-context |
| 100 | claude plugin install web-quality |
| 101 | claude plugin install frontend-tools |
| 102 | claude plugin install database-tools |
| 103 | ``` |
| 104 | |
| 105 | ## Development |
| 106 | |
| 107 | ### Workflow |
| 108 | |
| 109 | The project uses a structured workflow to keep versions, commands, and configurations in sync across Gemini and Claude platforms. |
| 110 | |
| 111 | ```mermaid |
| 112 | graph TD |
| 113 | subgraph "Phase 1: Sync Version" |
| 114 | P[package.json] -- sync-version --> AS[.agent-structurerc] |
| 115 | P -- sync-version --> M[.claude-plugin/marketplace.json] |
| 116 | P -- sync-version --> GE[gemini-extension.json] |
| 117 | end |
| 118 | |
| 119 | subgraph "Phase 2: Export to Claude" |
| 120 | CMD[commands/*.toml] -- export-claude --> P_CMD[plugins/commands/*.md] |
| 121 | SKL[skills/**] -- export-claude --> P_SKL[plugins/skills/**] |
| 122 | AS -- export-claude --> P_JSON[plugins/**/plugin.json] |
| 123 | P_JSON -- updates --> M |
| 124 | end |
| 125 | |
| 126 | subgraph "Phase 3: Distribute MCP" |
| 127 | AS -- distribute-mcp --> GE |
| 128 | AS -- distribute-mcp --> PM[plugins/company-context/.mcp.json] |
| 129 | end |
| 130 | ``` |
| 131 | |
| 132 | > **Note**: You must run `pnpm run build` before executing these commands, as they rely on the compiled files in the `dist/` directory. |
| 133 | |
| 134 | 1. **Sync Version**: Run `pnpm run sync-version` to propagate the version and name from `package.json` to `.agent-structurerc` (specifically `mainMcp`), `.claude-plugin/marketplace.json`, and `ge |