一键在 Manus 中运行任何 Skill

$pwd:

sync-context

Name: Sync Context
Author: thoughtfulllc

// Update context files to reflect current codebase state — new components, changed APIs, new patterns, and reasoning behind non-obvious decisions. Routes updates to the correct file based on what changed. Run after any significant design change before committing.

在 Manus 中运行

$ git log --oneline --stat

stars:332

forks:12

updated:2026年4月16日 02:46

SKILL.md

readonly

name	sync-context
description	Update context files to reflect current codebase state — new components, changed APIs, new patterns, and reasoning behind non-obvious decisions. Routes updates to the correct file based on what changed. Run after any significant design change before committing.

Update context files to reflect the current state of the codebase.

Step 1 — Gather what changed

git diff HEAD
git log --oneline -10
git diff HEAD --name-only | grep -E '\.(tsx|ts)$'

Step 2 — Classify each change and route to the correct file

Change type	Target file
New component, removed component, changed component props	`packages/ui/CLAUDE.md` (component catalog table)
New focus pattern, focus anti-pattern, useInteractive API change	`.claude/rules/focus-system.md`
New AI SDK convention, changed part types or states	`.claude/rules/ai-sdk.md`
New layout rule, intrinsic element, borderStyle	`.claude/rules/opentui-layout.md`
Non-obvious design decision worth preserving	`.claude/rules/design-decisions.md`
New docs convention, demo pattern	`packages/docs/CLAUDE.md`
New universal anti-pattern, import rule, test command	Root `CLAUDE.md`

Step 3 — For each update, evaluate

Is this new or already documented? (Don't duplicate)
Is the "why" non-obvious? (Only document if a future engineer might undo without understanding)
Is existing documentation still accurate? (Update or remove stale entries)
Is this a permanent pattern or temporary workaround? (Only document permanent)

Step 4 — Apply updates

Read the target file, then edit it following the existing format:

Component catalog: add/update row in the table
Rules: add section or update existing content
Anti-patterns: add - bullet item
Design decisions: add ## section with rationale

Step 5 — Verify

Root CLAUDE.md must stay under 100 lines
No duplicate information across files
All updated files have correct content

What NOT to add

Implementation details that belong in code comments
Tutorials or guides
Obvious decisions that don't need rationale
Bug workarounds or version-specific notes
Anything derivable from reading the code directly

related-skills.json

同仓库

create-component.md

from "thoughtfulllc/gridland"

Guide for creating a new UI component in @gridland/ui. Covers file structure, focus integration, keyboard handling, theme usage, JSDoc, export registration, and documentation.

2026-04-16332

production-ready.md

from "thoughtfulllc/gridland"

Review a component for production readiness as a UI framework. Assesses code quality, patterns, tests, docs, and API design. Produces a prioritized fix plan. Use before shipping a new or updated component to users.

2026-04-16332

audit-render.md

from "thoughtfulllc/gridland"

Audit the browser rendering pipeline for scissor/clipping bypass bugs. Use when touching browser-buffer.ts, canvas-painter.ts, or adding new visual features.

2026-04-13332

debug-layout.md

from "thoughtfulllc/gridland"

Diagnose layout issues in Gridland components. Spawns the layout-debugger agent with the relevant component. Use when a component renders incorrectly or layout looks wrong.

2026-04-13332

release-check.md

from "thoughtfulllc/gridland"

Pre-release checklist. Runs all 4 agents plus snapshot regression test, TypeScript check, and semver confirmation. Run before publishing a new package version.

2026-04-13332

review-docs.md

from "thoughtfulllc/gridland"

Documentation-focused review. Runs docs-mirror and dependency-auditor in parallel. Use after writing or updating documentation, demo components, or MDX pages.

2026-04-13332

package.json

"author": "thoughtfulllc"

"repository": "thoughtfulllc/gridland"

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

$ install --global

$ download --local

在 Manus 中运行

$ useful --forSOC

软件开发工程师计算机与数学类职业15-1252L4

name	sync-context
description	Update context files to reflect current codebase state — new components, changed APIs, new patterns, and reasoning behind non-obvious decisions. Routes updates to the correct file based on what changed. Run after any significant design change before committing.

Update context files to reflect the current state of the codebase.

Step 1 — Gather what changed

git diff HEAD
git log --oneline -10
git diff HEAD --name-only | grep -E '\.(tsx|ts)$'

Step 2 — Classify each change and route to the correct file

Change type	Target file
New component, removed component, changed component props	`packages/ui/CLAUDE.md` (component catalog table)
New focus pattern, focus anti-pattern, useInteractive API change	`.claude/rules/focus-system.md`
New AI SDK convention, changed part types or states	`.claude/rules/ai-sdk.md`
New layout rule, intrinsic element, borderStyle	`.claude/rules/opentui-layout.md`
Non-obvious design decision worth preserving	`.claude/rules/design-decisions.md`
New docs convention, demo pattern	`packages/docs/CLAUDE.md`
New universal anti-pattern, import rule, test command	Root `CLAUDE.md`

Step 3 — For each update, evaluate

Is this new or already documented? (Don't duplicate)
Is the "why" non-obvious? (Only document if a future engineer might undo without understanding)
Is existing documentation still accurate? (Update or remove stale entries)
Is this a permanent pattern or temporary workaround? (Only document permanent)

Step 4 — Apply updates

Read the target file, then edit it following the existing format:

Component catalog: add/update row in the table
Rules: add section or update existing content
Anti-patterns: add - bullet item
Design decisions: add ## section with rationale

Step 5 — Verify

Root CLAUDE.md must stay under 100 lines
No duplicate information across files
All updated files have correct content

What NOT to add

Implementation details that belong in code comments
Tutorials or guides
Obvious decisions that don't need rationale
Bug workarounds or version-specific notes
Anything derivable from reading the code directly

sync-context

Step 1 — Gather what changed

Step 2 — Classify each change and route to the correct file

Step 3 — For each update, evaluate

Step 4 — Apply updates

Step 5 — Verify

What NOT to add

同仓库更多 Skills

同仓库更多 Skills

Step 1 — Gather what changed

Step 2 — Classify each change and route to the correct file

Step 3 — For each update, evaluate

Step 4 — Apply updates

Step 5 — Verify

What NOT to add