paste-this-into-your-ai
Skill7 starsChanged 4 days agoMITView on GitHub
Write a paste-ready X post about one WongStack area (memory, the change loop, mini apps, browsing), or write or rewrite a site attachment with `attachment <slug>`; only when a person types it. Posts nothing.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- accessSkill
- browserSkill
- dailySkill
- memorySkill
- agent-browserSkill
- connectSkill
- improve-codeSkill
- lessonSkill
- reply-linkSkill
- uiSkill
- update-dependenciesSkill
- wong-setupSkill
- wong-syncSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Read this repo: it is WongStack's source, so it is the newest copy.
- Very specific: line 23
Start at wiki/README.md. Follow its links down to the area's pages.
- Distinctive: line 24
Read each of those pages in full.
- Distinctive: line 34
No section titles, no numbering, no emoji, no thread split.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Paste this into your AI
Explain one WongStack area well enough for a stranger to build it with their own AI. Two outputs share one style:
- A post (the default): one X post, printed in chat. Matthew posts it himself: never post to X.
- An attachment (
attachment <slug>): the filesite/attachments/<slug>.mdbehind one card on the site's Attachments page. Attachments owns its shape, its rules and its check.
The memory post is the model. Copy its shape and line style for both.
1. Read the area
Read this repo: it is WongStack's source, so it is the newest copy.
The area is the argument, such as memory, change loop, mini apps, or browsing. No argument: ask which area, with three or four areas as choices. For an attachment, the area is the file's sources:; a new slug has none yet, so pick them as below and list them.
- Start at
wiki/README.md. Follow its links down to the area's pages. If no link name matches, searchwiki/for the area's words. - Read each of those pages in full.
- Open each skill, script, hook, and rule those pages link, and read enough to know what each part does and when it runs.
2. Write it
Rules, all from the model:
- One opener line, then one empty line. A post opens like
How my Claude Code <does the thing>:; an attachment opens by its page's rule. - Then one flat list. Every line starts with
>and says one short clause. - A post has about 30 to 35 lines; an attachment about 15 to 30.
- No section titles, no numbering, no emoji, no thread split.
Cover, in this order where it fits: the parts and the job of each; how the parts link; when each step runs (session start, first edit, plan, build, ship, close, a schedule); how it stays clean; what wins when sources disagree.
Make it generic. A stranger must build it with their own tools: swap names by the generic-words table. Cut WongStack's name and any private repo's or person's name too.
Check it. Read each line back: does it start with > and hold one clause? Can a stranger follow it with no proper noun they lack? Do the lines together name each part, how the parts link, and when each step runs? Fix a line that fails, then count again.
3. Finish
A post
Print exactly these three things, in this order:
- The post in one fenced code block, so the
>marks copy as is. - One line: count the characters inside the block. 280 or fewer:
Fits a regular tweet (<n> characters).More:Needs a long post (<n> characters). - The reply in a second code block, word for word:
Or steal the source code here: https://github.com/matthewwong525/WongStackThe reply box is the last thing you print. A post writes nothing in this repo.
An attachment
Write site/attachments/<slug>.md with its frontmatter and the body, the last bullet pointing to this repo at the area's main page. Set checked: to today. Keep the order: an existing file has. Then run node scripts/check-attachments.mjs and fix what it names. Show the person the body in a code block, and end as the change loop does for a repo edit.
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.

