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.

跳到安装

仓库: ganesshkumar/ganesshkumar.github.io
最近来源活动: 2026年7月28日 15:01
检测到的 SKILL.md 语言: 英语
星标: 5
分支: 3

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

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

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

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

查看这个仓库的全部 Skills

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.