
0122 files · 164 KB
Agent desk
Give a standing job a plan, SQL memory and enforced limits, so your agent can pick it up tomorrow.
The library · 42 entries · 200 files
I’ve collected the instructions, software and project files I use for development and business operations. It includes agent skills, recurring workflows, application starters and setup guides.
Browse the entries and add the ones you need to your tray. After entering your email, you can download the files or copy an installation prompt for Claude Code or Codex. Private project information has been removed.
Add a desk, a skill or a whole shelf to your tray.
Every prompt, file and zip opens on this browser. Copy one prompt for your selection.
Give the prompt to Claude Code or Codex. It shows you the plan before writing.
Let your agent help you choose
Read https://withseismic.com/library/llms.txt, list the entries on each shelf and ask which I want. Show your installation plan before writing, and ask before overwriting any file.01 · Desks
A desk is a folder for an ongoing responsibility, such as business development. It contains a plan, rules, limits and a database schema for keeping records. The agent uses those records to continue the work between sessions.

0122 files · 164 KB
Give a standing job a plan, SQL memory and enforced limits, so your agent can pick it up tomorrow.
026 files · 35 KB
Keep companies, deals, calls and promises in one database, with the next decision ready for you.
033 files · 20 KB
Keep roles, CV versions, applications and follow-ups together, with your approval before applying.
02 · The stack
The starter brings together an account app, API and database. Use the complete project or take individual components for an existing codebase.

015 files · 152 KB
Start with accounts, organisations, email and analytics wired into a React app and Hono API.
025 files · 6 KB
Run builds, tests and type checks across your apps in dependency order, with cached results.
0316 files · 18 KB
Give your API typed routes, generated docs and a consistent error response before adding features.
048 files · 8 KB
Keep your database schema typed and your SQL migrations checked in beside the code that needs them.
052 files · 5 KB
Keep accounts, organisations and passkey sign-in in your own Hono API and Postgres database.
069 files · 10 KB
Keep React routes, session checks and cached server data working from the same types.
075 files · 5 KB
Check staged code at commit time and types before a push, including work written by your agents.
085 files · 10 KB
Deploy the folder you intended, run migrations first and check the change on the live site.
095 files · 11 KB
Use Loops for account email and signups, or write bespoke lifecycle journeys in TypeScript with Hogsend.
106 files · 26 KB
Define events once in TypeScript and build dashboards from those same names with a script.
03 · Skills
A skill records how a task should be done, including the context, output and checks. I develop these instructions with agents and revise them when actual use exposes a gap.

011 file · 6 KB
Tell your agent the job, the look and the stack, so it can write a skill you improve through use.
021 file · 9 KB
Keep a build moving from a plan in your repo to checks against the work running in production.
038 files · 68 KB
Rebuild a live design from its DOM, styles and motion, with evidence for each section.
041 file · 13 KB
Turn repeated styles into shared tokens, typed components and written rules your agent can follow.
053 files · 24 KB
Give your landing page one clear visual idea, with a written brief and measured type and spacing.
062 files · 14 KB
Build from a screenshot’s measured colours, type and geometry, with a tool to inspect the image.
0739 files · 419 KB
Turn sourced research into a branded PDF, with real interface captures and checks for overflowing pages.
082 files · 4 KB
Give Codex a full writing brief and have Claude check the result against the sources before applying it.
0920 files · 474 KB
Give your agent Railway’s own instructions for deploying services, reading logs and diagnosing databases.
104 files · 23 KB
Ask your agent for search performance, keyword demand and ad reports from the terminal.
111 file · 5 KB
Let your agent create and update Linear issues, projects and milestones through the command line.
04 · Guides
Instructions for connecting voice, search data and email to agent workflows. Each guide covers the accounts, permissions and configuration the setup needs.

0114 files · 77 KB
Let visitors talk through their needs, with call limits and the agent’s instructions fixed on your server.
021 file · 10 KB
Connect Search Console and Keyword Planner to the terminal, so your agent can inspect your search data.
031 file · 5 KB
See your Claude accounts’ limits beside the Mac’s notch and switch accounts without signing out.
044 files · 27 KB
Give your agent a mailbox on your domain, with API access controlled through Cloudflare Access.
051 file · 5 KB
Keep schema, crawl rules and search measurement together, with shared helpers and agent skills.
05 · Software
The entries explain how I use each application and where it fits into the work, from briefing and writing to running agents.

01Links
Put your agent inside the repo, where it can read the plan, run the skills and check its work.
02Links
Give the writing to the model I prefer for copy, while Claude checks every claim against its source.
03Links
Keep separate jobs open across Claude accounts, with Notch showing which account has room to work.
04Links
Speak the job, the look and the stack in one brief, so your agent gets the context together.
06Links
Give apps and tools their own shortcuts, so you can switch contexts from the keyboard.
07Links
Turn Caps Lock into all four modifiers, so new shortcuts don’t clash with app defaults.
08Links
Inspect API calls, so you can build connectors and tools on top of third-party services.
09Links
Build, test and deploy Cloudflare Workers from the command line, so deployment stays with the project.
10Links
Carry a visitor’s voice-agent answers into a call booking, so they don’t have to start again.
06 · Builders
Create a project plan, write a brief or check acceptance criteria. The tools help make the instructions specific enough to build and review. What you type stays in your browser.
01Runs in your browser
Give your agent a plan in the repo: instructions, decisions, a backlog and the first PRD.
02Runs in your browser
Find vague acceptance criteria and turn them into behaviours your agent can test.
I’ll send you one build log a week: what I added to the library and what I shipped with it. You can unsubscribe any time.