Frontend Module Standards
siteboon/claudecodeui
Enforces one repository's React and TypeScript module layout for code under src/: source-root imports, feature barrels, deliberate exports and no deep imports.
Qovery Console coding standards, architecture guidelines, naming conventions, testing practices, and development workflows.
Install Qovery Console Standards
$ npx skills add Qovery/console --skill qovery-console-standards -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Qovery/console qovery-console-standards --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/Qovery/console.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/qovery-console-standards .claude/skills/qovery-console-standards && 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 "qovery-console-standards" agent skill from https://github.com/Qovery/console/tree/staging/.agents/skills/qovery-console-standards into .claude/skills/qovery-console-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qovery-console-standards", 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/Qovery/console/tree/staging/.agents/skills/qovery-console-standardsType 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 Qovery/console --skill qovery-console-standards -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Qovery/console qovery-console-standards --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Qovery/console.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/qovery-console-standards .agents/skills/qovery-console-standards && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "qovery-console-standards" agent skill from https://github.com/Qovery/console/tree/staging/.agents/skills/qovery-console-standards into .agents/skills/qovery-console-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qovery-console-standards", 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 Qovery/console --skill qovery-console-standards -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Qovery/console qovery-console-standards --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Qovery/console.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/qovery-console-standards .cursor/skills/qovery-console-standards && 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 "qovery-console-standards" agent skill from https://github.com/Qovery/console/tree/staging/.agents/skills/qovery-console-standards into .cursor/skills/qovery-console-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qovery-console-standards", 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/Qovery/console.git --path .agents/skills/qovery-console-standards--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 Qovery/console --skill qovery-console-standards -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Qovery/console qovery-console-standards --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Qovery/console.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/qovery-console-standards .gemini/skills/qovery-console-standards && 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 "qovery-console-standards" agent skill from https://github.com/Qovery/console/tree/staging/.agents/skills/qovery-console-standards into .gemini/skills/qovery-console-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qovery-console-standards", 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 Qovery/console qovery-console-standardsInstalls 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 Qovery/console --skill qovery-console-standards -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Qovery/console.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/qovery-console-standards .github/skills/qovery-console-standards && 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 "qovery-console-standards" agent skill from https://github.com/Qovery/console/tree/staging/.agents/skills/qovery-console-standards into .github/skills/qovery-console-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qovery-console-standards", 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 Qovery/console --skill qovery-console-standards -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Qovery/console qovery-console-standards --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Qovery/console.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/qovery-console-standards .opencode/skills/qovery-console-standards && 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 "qovery-console-standards" agent skill from https://github.com/Qovery/console/tree/staging/.agents/skills/qovery-console-standards into .opencode/skills/qovery-console-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "qovery-console-standards", 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
qovery-console-standards- GitHub stars
- 227
- Token cost
- ~924 tokens
- SKILL.md length
- 318 words
- Files
- 9
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
Qovery Console coding standards, architecture guidelines, naming conventions, testing practices, and development workflows.
- Tasks that involve Code quality
- SKILL.md covers When to Apply, Rule Categories, Quick Reference and How to Use, plus 1 more section
- Calls nvm
- Tasks that involve Monorepo tooling
What it does
Qovery Console Standards is an agent skill from Qovery/console. Qovery Console coding standards, architecture guidelines, naming conventions, testing practices, and development workflows. This skill should be used when writing, reviewing, or refactoring code in the Qovery Console monorepo to ensure consistency and quality.
Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files (for example `AGENTS.md`, `rules/development-commands.md` and `rules/naming-conventions.md`).
It sits in Development, covering Code quality, Monorepo tooling and Refactoring. It works with React, TypeScript, Cypress and Storybook. The repository describes itself as: Qovery Web Console ⚡️. The licence is MIT.
When your agent uses it
- Tasks that involve Code quality
- Tasks that involve Monorepo tooling
- Tasks that involve Refactoring
Example prompts
- “/qovery-console-standards”
What it can do on your machine
Read from SKILL.md and the folder at commit caa50bf. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
nvm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Qovery Console Standards loads about 924 tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 318 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 Qovery/console at commit caa50bf, republished under its MIT licence (© Qovery). 318 words, ~924 tokens.
Download SKILL.mdSave it as
.claude/skills/qovery-console-standards/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.- name
- qovery-console-standards
- description
- Qovery Console coding standards, architecture guidelines, naming conventions, testing practices, and development workflows. This skill should be used when writing, reviewing, or refactoring code in the Qovery Console monorepo to ensure consistency and quality.
- license
- MIT
- metadata.author
- qovery
- metadata.version
- 1.0.0
Qovery Console Standards
Comprehensive coding standards for the Qovery Console React/TypeScript monorepo. Contains 7 rules covering architecture, React patterns, styling, testing, naming, development workflow, and pre-commit quality gates.
When to Apply
Reference these guidelines when:
- Writing new components, hooks, or utilities in the Console
- Reviewing or refactoring existing Console code
- Setting up tests for business logic
- Making styling decisions (Tailwind, Radix, accessibility)
- Running development commands or preparing commits
- Creating new Nx libraries or components
Rule Categories
| Rule | File | Scope |
|---|---|---|
| Project Architecture | project-architecture.md | Nx monorepo structure, lib organization, layer boundaries |
| React & TypeScript | react-typescript-standards.md | Import rules, component patterns, state management |
| Styling | styling-standards.md | TailwindCSS, Radix UI, responsive design, accessibility |
| Testing | testing-standards.md | Test setup, structure, mocking, coverage |
| Naming Conventions | naming-conventions.md | File, variable, component, and constant naming |
| Development Commands | development-commands.md | Daily workflow, Nx commands, package management, git |
| Pre-commit Workflow | pre-commit-workflow.md | Conventional commits, format/test/lint checks |
Quick Reference
Architecture
- Nx monorepo:
apps/andlibs/(domains, pages, shared) data-access= API logic,feature= business components,ui= reusable presentation- No circular imports; use Nx generators for new libs
React & TypeScript
- Inline type imports:
import { type Foo, bar } from './module' - Functional components only, no
React.FC, destructure props in signature - Route-scoped components read URL identifiers with TanStack Router
useParams({ strict: false }); do not forward route IDs through props solely for data access - React Query for server state,
clsx/twMergefor conditional classes
Styling
- TailwindCSS only, mobile-first, Radix UI for accessibility
- No inline styles, consistent spacing via Tailwind scale
Testing
renderWithProvidersfrom@qovery/shared/util-tests- Await
userEventinteractions; treatfireEventas deprecated unlessuserEventcannot represent the event and the exception is documented - Arrange-Act-Assert pattern
- Cover success, error, and edge states
Naming
- Snake-case files (
user-profile.tsx), PascalCase components Propssuffix for interfaces,UPPER_SNAKE_CASEfor constants
Workflow
- Yarn Berry only (never npm),
nvm use - Conventional commits:
feat|fix|chore(scope): message - Pre-commit: format -> test -> snapshot review -> lint
How to Use
Read individual rule files for detailed guidelines:
rules/project-architecture.md
rules/react-typescript-standards.md
rules/styling-standards.mdFull Compiled Document
For the complete guide with all rules expanded: AGENTS.md
© Qovery, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 8 other files in .agents/skills/qovery-console-standards of Qovery/console.
- SKILL.md
- AGENTS.md
- rules/development-commands.md
- rules/naming-conventions.md
- rules/pre-commit-workflow.md
- rules/project-architecture.md
- rules/react-typescript-standards.md
- rules/styling-standards.md
- rules/testing-standards.md
Open the folder on GitHubat commit caa50bf
Compare with similar skills
Qovery Console Standards 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 |
|---|---|---|---|---|---|---|
| Qovery Console Standards this skillQovery/console | 227 | — | ~924 | Automated safety check: Pass | MIT | |
| Frontend Module Standardssiteboon/claudecodeui | 14k | — | ~2.6k | Automated safety check: Pass | AGPL-3.0 | |
| Pnpm Engineteambit/bit | 18k | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Code Guidelinesgetsentry/sentry-react-native | 1.8k | — | ~3.2k | Automated safety check: Pass | MIT | |
| Coding Standardskurealnum/dotfiles | 290 | 17 repos | ~2.9k | Automated safety check: Pass | None | |
| Code Refactor Reviewkcsujeet/ilamy-calendar | 351 | 2 repos | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
Pnpm Engine
teambit/bit
Work on the pnpm Rust engine (@pnpm/napi, the pacquet crates) that bit install runs through.
- Official
Code Guidelines
getsentry/sentry-react-native
Enforce Sentry React Native SDK code guidelines for implementation, refactoring, and review.
Coding Standards
kurealnum/dotfiles
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
Code Refactor Review
kcsujeet/ilamy-calendar
Reviews code changes for reuse, composition, codebase consistency, and slop.
DRY Refactoring With jscpd
kucherenko/jscpd
Removes copy-paste duplication found by jscpd, starting with exact clones and hotspots, then renamed and near-miss copies, using proven refactoring strategies.
More from Qovery/console
Qovery UI
Qovery/console
Design review and implementation guidance for the Qovery Console.
Related
Works with
Categories
Questions about Qovery Console Standards
What does Qovery Console Standards do?
Qovery Console coding standards, architecture guidelines, naming conventions, testing practices, and development workflows. Qovery Console Standards is an agent skill from Qovery/console. Qovery Console coding standards, architecture guidelines, naming conventions, testing practices, and development workflows.
When should I use Qovery Console Standards?
Qovery Console Standards fits situations like: tasks that involve Code quality; tasks that involve Monorepo tooling; tasks that involve Refactoring.
How do I install Qovery Console Standards in Claude Code?
Run `npx skills add Qovery/console --skill qovery-console-standards -a claude-code`. Or copy the skill folder (.agents/skills/qovery-console-standards in Qovery/console) into .claude/skills/qovery-console-standards in your project. Claude Code loads it when a task matches its description.
How do I install Qovery Console Standards in Codex?
Run `npx skills add Qovery/console --skill qovery-console-standards -a codex`. Or copy the skill folder (.agents/skills/qovery-console-standards in Qovery/console) into .agents/skills/qovery-console-standards in your project. Codex loads it when a task matches its description.
Can I use Qovery Console Standards 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 Qovery/console --skill qovery-console-standards -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/qovery-console-standards, .gemini/skills/qovery-console-standards, .github/skills/qovery-console-standards and .opencode/skills/qovery-console-standards in your project.
What does Qovery Console Standards need to run?
Going by SKILL.md and its folder, Qovery Console Standards needs the command-line tools its instructions call (nvm).
Does Qovery Console Standards access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Qovery Console Standards 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 Qovery Console Standards use?
Qovery Console Standards is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Qovery Console Standards use?
About 924 tokens (SKILL.md is roughly 3.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 Qovery Console Standards?
Skills that share tags, products or a category with Qovery Console Standards: Frontend Module Standards (siteboon/claudecodeui, 14k stars), Pnpm Engine (teambit/bit, 18k stars), Code Guidelines (getsentry/sentry-react-native, 1.8k stars) and Coding Standards (kurealnum/dotfiles, 290 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Qovery Console Standards?
Qovery (a GitHub organization) maintains it in Qovery/console, which has 227 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 7, 2026.
Source: Qovery/console on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.