Menu
SkillsMP has collected 9 skills from ganesshkumar/ganesshkumar.github.io. Open a skill to review its source and details.
Showing 9 of 9 collected skills.
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…
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.
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.
Use when defining, revising, or reviewing the rebuild quality bar and KPI model in docs/quality-and-growth/performance-indicators.md; when deciding launch criteria, evaluation metrics, review cadence, traffic or trust KPIs, conversion KPIs, or how the project…
Use when managing project workspaces in projects/; when organizing priorities, roadmaps, execution trackers, reference notes, epics, features, user stories, tasks, or the front matter standard for project items.
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…
Use when defining, revising, or reviewing the site architecture in docs/content-and-information-architecture/system-design.md; when deciding page responsibilities, navigation structure, secondary surfaces, phased system growth, or cross-page structural rules…
Use when defining, revising, or reviewing the site’s UX patterns in docs/design-system/ux-patterns.md; when deciding typography, whitespace, spacing, colors, editorial rhythm, page layout patterns, component families, sidebars, reading flow, or design-system…
Use when defining, revising, or reviewing the project item schema in docs/work-item-standard.md; when deciding front matter fields, item taxonomy, body expectations, or placement rules for epics, features, user stories, and tasks under projects/.