core
Skill1 starsChanged 6 months agoNo licenceView on GitHub
AI co-creation operating system. Defines how Claude engages: as a peer second-brain, not an assistant. Challenge premises, strategic depth first, ship with momentum, ground decisions in meaning. Load for any interaction where you want Claude to think deeper and push back.
28 other projects use a version of this.
Adopted by
Most recently taken up by
- gkurt/ai-soulstheir own version, first seen Nov 8, 2026
- ouestlabs/audio-uitheir own version, first seen Nov 2, 2026
- vercel-labs/json-rendertheir own version, first seen Oct 29, 2026
- fishzjp/qa-skillstheir own version, first seen Oct 21, 2026
- ryu111/claude-workflow-configtheir own version, first seen Oct 20, 2026
- DATA-AI-XYZ/Tandemtheir own version, first seen Oct 15, 2026
Used with
Projects with it also use ts-core, native-ui and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
VercelSkillts-core
Authoring guide for the primary Native SDK app-logic path: TypeScript app cores - Model, Msg, update, and the pure functions they call, written in the closed app-core subset, checked by the @native-sdk/core frontend, and compiled ahead-of-time to native code by the external core compiler. Use for new apps unless the user explicitly chose Zig, when writing or modifying a src/core.ts app core, fixing subset checker errors (NS1001-NS1069), or deciding how to express state, messages, text (bytes and the byte-text string methods), text input, continuous controls (sliders, scroll), effects (Cmd), subscriptions (Sub), the host-event wiring channels (frameMsg, keyMsg, pinchMsg, dropMsg, appearanceMsg, chromeMsg, envMsgs, app manifest assets), derived values, the view_unbound lint opt-out, local mutation of owned arrays, or how to split a core into modules under src/ (relative imports, namespace imports, @native-sdk/core/text, @native-sdk/core/events). Use ts-services alongside this guide for src/services work.
Also in 3 projects that use this
- VercelSkill
native-ui
Authoring guide for the Native markup (.native) view tier of native-rendered Native SDK apps. TypeScript cores are the default and use this skill together with ts-core; Zig cores are an explicit alternative and this guide labels their lower-level UiApp recipes. Use when building or modifying native UI (widgets, layout, bindings, messages), writing .native files, wiring views to Model/Msg/update, testing markup views, or verifying a native app through the automation harness.
Also in 3 projects that use this
- +3 more from vercel-labs
Other versions28 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 28
- vercel-labs/agent-browser★ 47ksame name
- vercel-labs/json-render★ 19ksame name
- microsoft/data-formulator★ 17ksame name
- microsoft/RD-Agent★ 15ksame name
- vercel-labs/zero-native★ 7.8ksame name
- vercel-labs/native★ 7.8ksame name
- ouestlabs/audio-ui★ 202same name
- vercel-labs/issue-graph★ 163same name
- vercel-labs/xref★ 163same name
- fishzjp/qa-skills★ 62same name
18 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- carefulSkill
- codeSkill
- investigateSkill
- office-hoursSkill
- optimizeSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.