stack-and-design-decisions

Use when defining, revising, or reviewing implementation choices in docs/engineering/stack-decisions.md; when deciding framework, language, state management, styling direction, component sourcing, version policy, or stable UI implementation rules for the rebuild.

Ir para a instalação

Repositório: ganesshkumar/ganesshkumar.github.io
Última atividade na origem: 28 de julho de 2026 às 15:01
Idioma detectado do SKILL.md: inglês
Estrelas: 5
Forks: 3

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

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ê.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/ganesshkumar/ganesshkumar.github.io --skill stack-and-design-decisions

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

content-and-sidebar-strategy

Use when defining, revising, or reviewing content, sidebar, and monetization behavior in docs/quality-and-growth/content-and-sidebar-strategy.md; when deciding sidebar placement, suggestion logic, ad zones, sponsor or affiliate patterns, or reading-safe monetization rules for the rebuild.

2026-07-28

docs-authoring

Use when writing, revising, or reviewing docs in docs/; when deciding whether content belongs in docs/ versus projects/ or skills/; when maintaining the docs graph, system design, UX, stack, content, or quality documents.

2026-07-28

page-creation-and-review

Use when creating a new website page or reviewing an existing page; when deciding page purpose, required content, structural ownership, UX fit, or whether the page should exist at all.

2026-07-28

Ver todas deste repositório

Stack And Design Decisions

What this skill is for

Use this skill when a task affects the technical implementation policy of the site.

It covers:

framework and runtime choices,

language and type policy,

styling direction,

component sourcing,

state management defaults,

version policy,

and stable implementation constraints for UI work.

Default file targets

docs/engineering/stack-decisions.md

docs/content-and-information-architecture/system-design.md

docs/design-system/ux-patterns.md

docs/README.md

What belongs here

Use this skill for questions such as:

should this be built with the documented stack,

when should a new dependency be introduced,

when is shared state justified,

whether a component should come from shadcn/ui or be bespoke,

and how styling should remain stable and maintainable.

Decision rules

If the change affects implementation defaults or reusable engineering policy, it belongs here.

If the change is mostly about architecture, coordinate with system-design.

If the change is mostly about visual rhythm or layout behavior, coordinate with ux-patterns.

How to work

Start with docs/engineering/stack-decisions.md as the implementation source of truth.

Prefer stable, durable choices over novelty.

Justify new dependencies against the existing stack.

Reuse documented component families before introducing bespoke primitives.

Keep state local unless there is a real multi-route or multi-module need.

Output expectation

When using this skill, explain:

which implementation rule changed,

what default future agents should now assume,

whether the change alters dependency or component policy,

and which adjacent docs must stay aligned.

name	stack-and-design-decisions
user-invocable	false
description	Use when defining, revising, or reviewing implementation choices in docs/engineering/stack-decisions.md; when deciding framework, language, state management, styling direction, component sourcing, version policy, or stable UI implementation rules for the rebuild.