Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

web

Estrelas3

Forks0

Atualizado19 de maio de 2026 às 12:22

Web frontend engineering conventions for team. Vue.js stack. Project conventions in .claude/conventions/web.md override these defaults.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

Pierry

Pierry/harness-kit

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	web
description	Web frontend engineering conventions for team. Vue.js stack. Project conventions in .claude/conventions/web.md override these defaults.
user_invocable	false

Web frontend conventions, team default.

Project override: if {repo}/.claude/conventions/web.md exists, overrides any rule here. See guides/conventions-override.md.

Defaults (team frontend stack)

Stack:

Vue 2.6 Options API. Avoid Composition API unless repo already uses Vue 3.
Vuex with namespaced modules: createNamespacedHelpers.
TMS Design System: IpPageBase, IpTabs, IpFormField, IpSelect, IpDialog, IpSnackbar.
PrimeVue 2.10 alongside TMS in some repos.
@team-js packages: secure-components, secure-providers, secure-ui.
Feature folders: /features/private, /features/public.

Component order:

data, computed, watch, created/mounted, methods, components.

Styling:

Scoped SCSS.
BEM-like naming.
CSS variables for theming.

UX feedback:

Snackbar via this.$ipSnackbar.add().
Async: .catch() before .finally(). Toast on failure.

State:

Vuex actions for side effects, mutations for state changes.
Getters for derived state.

Tests:

Vitest or Jest depending on repo.
Vue Test Utils for component tests.
Cover happy path, error path, edge case.

Before writing code

Read at least 3 similar components in repo to confirm:

Vue version (2 vs 3)
API style (Options vs Composition)
Design system in use (TMS, PrimeVue, custom)
State management (Vuex, Pinia, none)

Never assume.

Forbidden in PR

Composition API in Vue 2 repos
Inline styles when SCSS exists
Direct mutation of Vuex state outside mutations
Components without tests
console.log in production code

Mark gaps

<!-- TBD - verify with tech lead: {what you searched, what is missing} -->

Mais deste repositório

mesmo repositório

designer

Pierry/harness-kit

Visual + UX design defaults for new UIs. Material Design 3, dark/light theme, modern type, Behance-grade polish, i18n (en, pt-BR, es), context-aware favicon. No emojis and no em-dashes; use MD3/modern icons instead. Apply when building something new. Project conventions in .claude/conventions/web.md override these defaults.

2026-06-243

update

Pierry/harness-kit

Re-install / upgrade harness-kit in the current project to the version bundled in the installed plugin. Run after /plugin update harness-kit fetches a newer plugin version.

2026-06-193

prp

Pierry/harness-kit

Generate a Product Requirements Prompt for engineering handoff. Needs an approved PRD. Sensors, link validation, and eval gates.

2026-06-153

install

Pierry/harness-kit

Install the harness-kit pipeline into the current project. Copies agents, slash commands, skills, hooks, and the status bar into the project's .claude/, plus AGENTS.md and CLAUDE.md at the repo root. Run after adding the harness-kit plugin from the marketplace.

2026-06-153

design

Pierry/harness-kit

Design any system from scratch into a rigorous System Design Doc. Generic fallback when no topic-specific playbook fits. Sensors and evals gate.

2026-06-153

rate-limiter

Pierry/harness-kit

Design a distributed rate limiter at scale, policy model, enforcement layers (edge/gateway/service), algorithms (token bucket, sliding window), hot keys, fail-open vs fail-closed, multi-region, shadow mode. Topic playbook from the System Design series EP (Rate Limit

2026-06-153

name	web
description	Web frontend engineering conventions for team. Vue.js stack. Project conventions in .claude/conventions/web.md override these defaults.
user_invocable	false

Web frontend conventions, team default.

Project override: if {repo}/.claude/conventions/web.md exists, overrides any rule here. See guides/conventions-override.md.

Defaults (team frontend stack)

Stack:

Vue 2.6 Options API. Avoid Composition API unless repo already uses Vue 3.
Vuex with namespaced modules: createNamespacedHelpers.
TMS Design System: IpPageBase, IpTabs, IpFormField, IpSelect, IpDialog, IpSnackbar.
PrimeVue 2.10 alongside TMS in some repos.
@team-js packages: secure-components, secure-providers, secure-ui.
Feature folders: /features/private, /features/public.

Component order:

data, computed, watch, created/mounted, methods, components.

Styling:

Scoped SCSS.
BEM-like naming.
CSS variables for theming.

UX feedback:

Snackbar via this.$ipSnackbar.add().
Async: .catch() before .finally(). Toast on failure.

State:

Vuex actions for side effects, mutations for state changes.
Getters for derived state.

Tests:

Vitest or Jest depending on repo.
Vue Test Utils for component tests.
Cover happy path, error path, edge case.

Before writing code

Read at least 3 similar components in repo to confirm:

Vue version (2 vs 3)
API style (Options vs Composition)
Design system in use (TMS, PrimeVue, custom)
State management (Vuex, Pinia, none)

Never assume.

Forbidden in PR

Composition API in Vue 2 repos
Inline styles when SCSS exists
Direct mutation of Vuex state outside mutations
Components without tests
console.log in production code

Mark gaps

<!-- TBD - verify with tech lead: {what you searched, what is missing} -->