一键在 Manus 中运行任何 Skill

what-i-want-to-exist-projects

星标4

分支2

更新时间2026年7月6日 18:32

Use when adding, updating, or reviewing entries for the schalkneethling.com "What I want to exist" projects area, including project cards, project detail pages, repo doc cache refreshes, GOAL.md/ROADMAP.md links, and the little demos section.

安装

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

在 Manus 中运行

来源

schalkneethling

schalkneethling/schalkneethling.com

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

What I Want To Exist Projects

Use this skill for changes under src/content/projects/, src/pages/projects*, src/components/Projects/, src/data/project-doc-cache/, or tests that protect the curated project listing and detail pages.

Workflow

Read the current project entry or nearby entries in src/content/projects/.
If adding or materially updating a project, inspect the repo, cached docs, and public project page context before writing summaries.
Keep public page copy editorial: summarize GOAL.md, ROADMAP.md, issues, and repo docs instead of pasting long verbatim source text.
Preserve the current card/detail conventions:
- /projects remains the listing URL.
- Cards link to internal /projects/{slug} pages.
- Every card needs an imageUrl.
- category: "main" appears in the Projects section.
- category: "demo" appears in Little demos.
Update tests before implementation when behavior or required content changes.
Run the narrow relevant tests first, then the site checks listed below.

Adding Or Updating A Project

For schema details and a frontmatter checklist, read references/project-entry.md.

Use the project slug as the filename in src/content/projects/{slug}.md. Keep ordering deliberate. Do not automate project ordering unless the user asks.

If repo docs changed, run:

pnpm run refresh:project-docs

Review the generated cache diff under src/data/project-doc-cache/. The cache is source material for editorial summaries, not content rendered directly into the public pages.

Validation

Run the smallest meaningful test first. Common commands:

pnpm exec vitest run tests/projectContent.test.ts
pnpm exec vitest run tests/projectFilters.test.ts tests/projectPages.test.ts
pnpm exec vitest run tests/projectDocCache.test.ts
pnpm exec vitest run tests/projectSkill.test.ts
pnpm run typecheck
pnpm run build
pnpm run test:a11y

For listing or detail page UI changes, include the relevant Playwright coverage in tests/projects.spec.ts and verify accessibility.

同仓库更多 Skills

同仓库

dependabot-config

schalkneethling/schalkneethling.com

Generate or update Dependabot configuration files for projects. Use this skill whenever the user asks to add, create, update, configure, or fix Dependabot for a project — including phrases like "set up Dependabot", "add Dependabot config", "update my dependabot.yml", "enable Dependabot updates", or "configure automated dependency updates". Always apply this skill even if the user only mentions one ecosystem (e.g. "add Dependabot for npm") — the canonical config covers all required ecosystems.

2026-05-234

npm-package-publishing

schalkneethling/schalkneethling.com

Apply best practices when publishing npm packages, including secure CI/CD workflows, trusted publishing via OIDC, GitHub repository hardening, and supply-chain attack prevention. Use this skill whenever the user asks about publishing an npm package, setting up a publish workflow, configuring GitHub Actions for release automation, managing npm tokens or secrets, setting up changesets, or auditing an existing publishing pipeline for security. Also trigger when the user mentions publint, OIDC trusted publishing, release automation, or package versioning workflows.

2026-05-234

name	what-i-want-to-exist-projects
description	Use when adding, updating, or reviewing entries for the schalkneethling.com "What I want to exist" projects area, including project cards, project detail pages, repo doc cache refreshes, GOAL.md/ROADMAP.md links, and the little demos section.

What I Want To Exist Projects

Workflow

Read the current project entry or nearby entries in src/content/projects/.
If adding or materially updating a project, inspect the repo, cached docs, and public project page context before writing summaries.
Keep public page copy editorial: summarize GOAL.md, ROADMAP.md, issues, and repo docs instead of pasting long verbatim source text.
Preserve the current card/detail conventions:
- /projects remains the listing URL.
- Cards link to internal /projects/{slug} pages.
- Every card needs an imageUrl.
- category: "main" appears in the Projects section.
- category: "demo" appears in Little demos.
Update tests before implementation when behavior or required content changes.
Run the narrow relevant tests first, then the site checks listed below.

Adding Or Updating A Project

For schema details and a frontmatter checklist, read references/project-entry.md.

Use the project slug as the filename in src/content/projects/{slug}.md. Keep ordering deliberate. Do not automate project ordering unless the user asks.

If repo docs changed, run:

pnpm run refresh:project-docs

Review the generated cache diff under src/data/project-doc-cache/. The cache is source material for editorial summaries, not content rendered directly into the public pages.

Validation

Run the smallest meaningful test first. Common commands:

pnpm exec vitest run tests/projectContent.test.ts
pnpm exec vitest run tests/projectFilters.test.ts tests/projectPages.test.ts
pnpm exec vitest run tests/projectDocCache.test.ts
pnpm exec vitest run tests/projectSkill.test.ts
pnpm run typecheck
pnpm run build
pnpm run test:a11y

For listing or detail page UI changes, include the relevant Playwright coverage in tests/projects.spec.ts and verify accessibility.