Run any Skill in Manus with one click

repo-homepage-grid-registry

Stars17

Forks0

UpdatedApril 27, 2026 at 08:32

Maintains homepage registry data, grid item types, shuffled layout behavior, reader panels, and homepage block wiring. Use when editing `src/lib/registry/homepage.ts`, `src/lib/types/homepage.ts`, grid components, homepage blocks, or `src/routes/+page.svelte`.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

emzinnia

emzinnia/emzinnia.dev

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	repo-homepage-grid-registry
description	Maintains homepage registry data, grid item types, shuffled layout behavior, reader panels, and homepage block wiring. Use when editing `src/lib/registry/homepage.ts`, `src/lib/types/homepage.ts`, grid components, homepage blocks, or `src/routes/+page.svelte`.

Repo Homepage Grid Registry

Use this skill when

Adding, removing, or reordering homepage projects, articles, or special blocks
Changing GridItem, FeaturedItem, or homepage registry types
Editing src/routes/+page.svelte, grid components, or homepage block composition
Updating reader panel selection for article or project cards

Source-of-truth split

Project and homepage registry data lives in src/lib/registry/homepage.ts.
Grid item unions live in src/lib/types/homepage.ts.
Grid layout state lives in src/lib/stores/gridLayoutStore.svelte.ts.
Reader panel state lives in src/lib/stores/readerPanelStore.svelte.ts.
Grid UI lives in src/lib/components/grids/.
Homepage-specific blocks live in src/lib/components/blocks/.

Rules

Keep ProjectId, projectRegistry, and projectIds in sync.
Keep GridItem variants aligned with the blocks that src/routes/+page.svelte can render.
Preserve the seeded shuffle behavior unless the layout requirement explicitly changes.
Treat article registry entries as derived from defaultArticles; do not duplicate article metadata manually.
Update reader panel behavior when adding a card type that opens article or project detail.
Consider /editor impact for changes that share gridLayoutStore or user settings.

Verification

Run npm run check for registry or route changes.
Run npm run test:unit -- --run when changing shuffle, neighbor, layout store, or selection helpers.
Manually verify homepage cards, reader panels, and /editor/grid when layout or registry behavior changes.

More from this repository

same repository

repo-content-markdown-workflow

emzinnia/emzinnia.dev

Maintains article, project, and markdown-backed content flows in this SvelteKit portfolio. Use when editing `src/articles/**`, blog/project routes, `src/lib/articles.ts`, `src/lib/markdown.ts`, content reader panels, or the dev content editor.

2026-04-2717

repo-design-system-catalog

emzinnia/emzinnia.dev

Maintains this repo's UI component library, design page, component documentation registry, and design-system docs. Use when editing `src/lib/components/ui/**`, `src/lib/components/design/**`, `src/lib/registry/designComponents.ts`, `src/routes/design/**`, or `docs/components/**`.

2026-04-2717

repo-performance-analytics-workflow

emzinnia/emzinnia.dev

Maintains the dev performance analytics pipeline across browser instrumentation, persisted analytics API, Prisma storage, and editor analytics UI. Use when editing `performanceAnalytics`, `/api/performance-analytics`, analytics Prisma models, or editor analytics sections.

2026-04-2717

repo-api-route-patterns

emzinnia/emzinnia.dev

Implements SvelteKit API routes in this repo using the existing server, env, and response conventions. Use when editing `src/routes/api/**/+server.ts`, adding new endpoints, or connecting server routes to Prisma or GitHub-backed data.

2026-04-1117

repo-editor-dev-surface

emzinnia/emzinnia.dev

Maintains the dev-only editor route and its shared homepage customization state. Use when changing `/editor`, grid layout behavior, local user settings, debug toggles, or editor section components.

2026-04-1117

repo-hero-3d-workflow

emzinnia/emzinnia.dev

Updates the homepage hero 3D effect across Threlte scene code, parameter stores, and persisted debug settings. Use when changing `Hero3D`, shader parameters, presets, motion tuning, or hero debug controls.

2026-04-1117

name	repo-homepage-grid-registry
description	Maintains homepage registry data, grid item types, shuffled layout behavior, reader panels, and homepage block wiring. Use when editing `src/lib/registry/homepage.ts`, `src/lib/types/homepage.ts`, grid components, homepage blocks, or `src/routes/+page.svelte`.

Repo Homepage Grid Registry

Use this skill when

Adding, removing, or reordering homepage projects, articles, or special blocks
Changing GridItem, FeaturedItem, or homepage registry types
Editing src/routes/+page.svelte, grid components, or homepage block composition
Updating reader panel selection for article or project cards

Source-of-truth split

Project and homepage registry data lives in src/lib/registry/homepage.ts.
Grid item unions live in src/lib/types/homepage.ts.
Grid layout state lives in src/lib/stores/gridLayoutStore.svelte.ts.
Reader panel state lives in src/lib/stores/readerPanelStore.svelte.ts.
Grid UI lives in src/lib/components/grids/.
Homepage-specific blocks live in src/lib/components/blocks/.

Rules

Keep ProjectId, projectRegistry, and projectIds in sync.
Keep GridItem variants aligned with the blocks that src/routes/+page.svelte can render.
Preserve the seeded shuffle behavior unless the layout requirement explicitly changes.
Treat article registry entries as derived from defaultArticles; do not duplicate article metadata manually.
Update reader panel behavior when adding a card type that opens article or project detail.
Consider /editor impact for changes that share gridLayoutStore or user settings.

Verification

Run npm run check for registry or route changes.
Run npm run test:unit -- --run when changing shuffle, neighbor, layout store, or selection helpers.
Manually verify homepage cards, reader panels, and /editor/grid when layout or registry behavior changes.