remorses
53 verified skills58,101 total stars
playwriter/src
## CLI Usage If `playwriter` command is not found, install globally or use npx/bunx: ```bash npm install -g playwriter@latest # or use without installing: npx playwriter@latest session new bunx playwriter@latest session new ``` If using npx or bunx always use @latest for the first session command. so we are sure of using the latest version of the package ### Session management Each session runs in an **isolated sandbox** with its own `state` object. Use sessions to: - Keep state separate b
tools3,557
playwriter
Control the user own Chrome browser via Playwriter extension with Playwright code snippets in a stateful local js sandbox via playwriter cli. Use this over other Playwright MCPs to automate the browser — it connects to the user's existing Chrome instead of launching a new one. Use this for JS-heavy websites (Instagram, Twitter, cookie/login walls, lazy-loaded UIs) instead of webfetch/curl. Run `playwriter skill` command to read the complete up to date skill
tools3,348
critique
Git diff viewer. Renders diffs as web pages, images, and PDFs with syntax highlighting. Use this skill when working with critique for showing diffs, generating diff URLs, or selective hunk staging.
development1,146
npm-package
Opinionated TypeScript npm package template for ESM packages. Enforces src→dist builds with tsc, strict TypeScript defaults, explicit exports, and publish-safe package metadata. Use this when creating or updating any npm package in this repo.
development1,138
new-skill
Best practices for creating a SKILL.md file. Covers file structure, frontmatter, writing style, and where to place skills in a repository. Use when the user wants to create a new skill, update an existing skill, write a SKILL.md, or asks how skills work.
documentation1,130
new-skill
Best practices for creating a SKILL.md file. Covers file structure, frontmatter, writing style, and where to place skills in a repository. Use when the user wants to create a new skill, update an existing skill, write a SKILL.md, or asks how skills work.
documentation1,087
egaki
AI image and video generation CLI. Use this skill to install egaki, configure auth, run help commands, and generate images or videos with provider keys or an Egaki subscription.
tools1,052
proxyman
Reverse-engineer HTTP APIs using Proxyman for macOS. Intercept, record, and export network traffic from CLI tools and apps (Node.js, Python, Ruby, Go, curl). Export as HAR (JSON) and analyze with jq. Use this skill when the user wants to capture, inspect, or reverse-engineer HTTP traffic from macOS applications.
tools1,052
tuistory
Control and monitor terminal applications. Supports running TUI processes in background. TMUX replacement for agents. Can control fully interactive TUI apps like claude or opencode. Use tuistory and read the skill when you need to: - Run background processes for agents like dev servers. prefer it over `tmux` because it waits for real output instead of guessing with `sleep` - Control interactive CLIs and TUIs by typing, pressing keys, clicking, waiting, and taking snapshots - Write Playwright-style tests for terminal apps with `vitest` or `bun:test` It has **2 modes**: - **CLI** (`tuistory`) for persistent background sessions and terminal automation. **Run `tuistory --help` first.** - **JS/TS API** (`launchTerminal`) for writing tests (like playwright for TUIs) and programmatic control in scripts.
tools1,052
errore
errore is Go-style error handling for TypeScript: return errors instead of throwing them. Instead of Go's two-value tuple (val, err), functions return a single Error | T union. Instead of checking err != nil, you check instanceof Error. TypeScript narrows the type automatically — forget to check and your code won't compile. No wrapper types, no Result monads, just unions and instanceof. The errore npm package provides helper utilities (createTaggedError, tryAsync, matchError, findCause, partition) but the core pattern is zero-dependency. Benefits: every error is visible in the return type, callers can't forget to handle errors, flat control flow with early returns instead of nested try-catch, and errors carry typed properties with cause chains for debugging. ALWAYS read this skill when a repo uses the errore "errors as values" convention (errore.org). ALWAYS use errore for new TypeScript projects.
tools1,052
event-sourcing-state
Event-sourced application state pattern for TypeScript apps. Prefer bounded event logs plus pure derivation functions over mirrored mutable lifecycle flags. Use when state transitions are driven by events and bugs can be reproduced from a saved event stream.
development1,052
lintcn
Type-aware TypeScript lint rules in .lintcn/ Go files. Only load this skill when creating, editing, or debugging rule files. To just run the linter: `npx lintcn lint` (or `--fix`, `--tsconfig <path>`). Finds .lintcn/ by walking up from cwd. First build ~30s, cached ~1s. In monorepos, run from each package folder, not the root. Warnings don't fail CI and only show for git-changed files by default. Use `--all-warnings` to see them across the entire codebase.
development1,052
opensrc
Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for", "read the source of", "how does X work internally", "get the implementation of", "opensrc path", or any task requiring access to dependency source code beyond types and docs.
development1,052
playwriter
Control the user own Chrome browser via Playwriter extension with Playwright code snippets in a stateful local js sandbox via playwriter cli. Use this over other Playwright MCPs to automate the browser — it connects to the user's existing Chrome instead of launching a new one. Use this for JS-heavy websites (Instagram, Twitter, cookie/login walls, lazy-loaded UIs) instead of webfetch/curl. Run `playwriter skill` command to read the complete up to date skill
tools1,052
security-review
Complete a security review of the pending changes on the current branch. Performs a focused, high-confidence security audit with detailed false-positive filtering. Use when the user wants a security review of their PR or branch changes.
testing1,052
sigillo
Sigillo is a self-hostable open-source alternative to Doppler. Use when working with sigillo run, sigillo setup, sigillo login, managing secrets, projects, or environments. Also load when integrating Sigillo into CI, Cloudflare Workers, Docker, Vercel, or any other deployment target.
testing1,052
spiceflow
Spiceflow is a super simple, fast, and type-safe API and React Server Components framework for TypeScript. Works on Node.js, Bun, and Cloudflare Workers. Use this skill whenever working with spiceflow to get the latest docs and API reference.
development1,052
spiceflow
Spiceflow is a super simple, fast, and type-safe API and React Server Components framework for TypeScript. Works on Node.js, Bun, and Cloudflare Workers. Use this skill whenever working with spiceflow to get the latest docs and API reference.
development1,052
tuistory
Control and monitor terminal applications. Supports running TUI processes in background. TMUX replacement for agents. Can control fully interactive TUI apps like claude or opencode. Use tuistory and read the skill when you need to: - Run background processes for agents like dev servers. prefer it over `tmux` because it waits for real output instead of guessing with `sleep` - Control interactive CLIs and TUIs by typing, pressing keys, clicking, waiting, and taking snapshots - Write Playwright-style tests for terminal apps with `vitest` or `bun:test` It has **2 modes**: - **CLI** (`tuistory`) for persistent background sessions and terminal automation. **Run `tuistory --help` first.** - **JS/TS API** (`launchTerminal`) for writing tests (like playwright for TUIs) and programmatic control in scripts.
tools1,052
usecomputer
Desktop automation CLI for AI agents (macOS, Linux, Windows). Screenshot, click, type, scroll, drag with native Zig backend. Use this skill when automating desktop apps with computer use models (GPT-5.4, Claude). Covers the screenshot-action feedback loop, coord-map workflow, window-scoped screenshots, and system prompts for accurate clicking.
tools1,052
x-articles
Edit x.com (Twitter) long-form article drafts reliably. Use this for markdown imports, bulk formatting, code blocks, headings, lists, and repeated inline styling. Inspect and validate with Playwriter, but prefer x.com (Twitter) article GraphQL mutations for deterministic updates.
development1,052
zele
zele is a multi-account email and calendar CLI for Gmail, IMAP/SMTP (Fastmail, Outlook, any provider), and Google Calendar. It reads, searches, sends, replies, forwards, archives, stars, and trashes emails, manages drafts, labels, attachments, and Gmail filters, and creates, updates, and deletes calendar events with RSVP and free/busy support. Output is YAML so commands can be piped through yq and xargs. ALWAYS load this skill when the user asks to check email, read/send messages, reply or forward, archive or trash threads, manage drafts or labels, download attachments, schedule meetings, check their calendar, RSVP to events, or when they run any `zele` command. Load it before writing any code or shell commands that touch zele so you know the correct subcommand structure, the Google vs IMAP feature matrix, the headless login flow, and the agent-specific rules.
tools1,052
zele
zele is a multi-account email and calendar CLI for Gmail, IMAP/SMTP (Fastmail, Outlook, any provider), and Google Calendar. It reads, searches, sends, replies, forwards, archives, stars, and trashes emails, manages drafts, labels, attachments, and Gmail filters, and creates, updates, and deletes calendar events with RSVP and free/busy support. Output is YAML so commands can be piped through yq and xargs. ALWAYS load this skill when the user asks to check email, read/send messages, reply or forward, archive or trash threads, manage drafts or labels, download attachments, schedule meetings, check their calendar, RSVP to events, or when they run any `zele` command. Load it before writing any code or shell commands that touch zele so you know the correct subcommand structure, the Google vs IMAP feature matrix, the headless login flow, and the agent-specific rules.
tools1,052
zustand-centralized-state
Centralized state management pattern using Zustand vanilla stores. One immutable state atom, functional transitions via setState(), and a single subscribe() for all reactive side effects. Based on Rich Hickey's "Simple Made Easy" principles: prefer values over mutable state, derive instead of cache, centralize transitions, and push side effects to the edges. Resource co-location in the same store is also valid when lifecycle management is safer that way. Also covers state encapsulation: keeping state local to its owner (closures, plugins, factory functions) so it doesn't leak across the app, reducing the blast radius of mutations. Also covers event sourcing: keeping a bounded event buffer and deriving state with pure functions instead of mutable flags, making event handlers easy to test and reason about. Use this skill when building any stateful TypeScript application (servers, extensions, CLIs, relays) to keep state simple, testable, and easy to reason about. ALWAYS read this skill when a project uses zustand/vanilla for state management outside of React.
tools1,052
npm-package
Opinionated TypeScript npm package template for ESM packages. Enforces src→dist builds with tsc, strict TypeScript defaults, explicit exports, and publish-safe package metadata. Use this when creating or updating any npm package in this repo.
development1,052
batch
Research and plan a large-scale change, then execute it in parallel across 5-30 isolated worktree agents that each open a PR. Use when the user wants to make a sweeping, mechanical change across many files (migrations, refactors, bulk renames) that can be decomposed into independent parallel units.
development1,052
jitter
Control Jitter (jitter.video) for exporting animations, replacing assets, and modifying text programmatically via Playwriter.
testing1,052
profano
CLI tool to analyze V8 .cpuprofile files and print top functions by self-time or total-time in the terminal. ALWAYS load this skill when CPU profiling JavaScript or TypeScript programs (Node, Vitest, Bun, Chrome DevTools exports) — it shows how to generate .cpuprofile files and how to inspect them from the terminal without opening Chrome DevTools.
tools1,052
critique
Git diff viewer. Renders diffs as web pages, images, and PDFs with syntax highlighting. Use this skill when working with critique for showing diffs, generating diff URLs, or selective hunk staging.
development1,052
simplify
Review changed code for reuse, quality, and efficiency, then fix any issues found. Use when the user wants to clean up, simplify, or review recently changed code. Launches three parallel review agents (code reuse, code quality, efficiency) and aggregates findings.
development1,052
termcast
Build TUIs with a Raycast-like React API using termcast. Implements @raycast/api components (List, Detail, Form, Action) rendered to the terminal via opentui.
development1,052
goke
goke is a zero-dependency, type-safe CLI framework for TypeScript. CAC replacement with Standard Schema support (Zod, Valibot, ArkType). Use goke when building CLI tools — it handles commands, subcommands, options, type coercion, help generation, and more. Schema-based options give you automatic type inference, coercion from strings, and help text generation. ALWAYS read this skill when a repo uses goke for its CLI.
tools1,052
goke
goke is a zero-dependency, type-safe CLI framework for TypeScript. CAC replacement with Standard Schema support (Zod, Valibot, ArkType). Use goke when building CLI tools — it handles commands, subcommands, options, type coercion, help generation, and more. Schema-based options give you automatic type inference, coercion from strings, and help text generation. ALWAYS read this skill when a repo uses goke for its CLI.
tools1,047
batch
Research and plan a large-scale change, then execute it in parallel across 5-30 isolated worktree agents that each open a PR. Use when the user wants to make a sweeping, mechanical change across many files (migrations, refactors, bulk renames) that can be decomposed into independent parallel units.
development1,030
profano
CLI tool to analyze V8 .cpuprofile files and print top functions by self-time or total-time in the terminal. ALWAYS load this skill when CPU profiling JavaScript or TypeScript programs (Node, Vitest, Bun, Chrome DevTools exports) — it shows how to generate .cpuprofile files and how to inspect them from the terminal without opening Chrome DevTools.
tools1,030
termcast
Build TUIs with a Raycast-like React API using termcast. Implements @raycast/api components (List, Detail, Form, Action) rendered to the terminal via opentui.
development1,027
security-review
Complete a security review of the pending changes on the current branch. Performs a focused, high-confidence security audit with detailed false-positive filtering. Use when the user wants a security review of their PR or branch changes.
testing1,027
usecomputer
Desktop automation CLI for AI agents (macOS, Linux, Windows). Screenshot, click, type, scroll, drag with native Zig backend. Use this skill when automating desktop apps with computer use models (GPT-5.4, Claude). Covers the screenshot-action feedback loop, coord-map workflow, window-scoped screenshots, and system prompts for accurate clicking.
tools1,027
playwriter
Control the user own Chrome browser via Playwriter extension with Playwright code snippets in a stateful local js sandbox via playwriter cli. Use this over other Playwright MCPs to automate the browser — it connects to the user's existing Chrome instead of launching a new one. Use this for JS-heavy websites (Instagram, Twitter, cookie/login walls, lazy-loaded UIs) instead of webfetch/curl. Run `playwriter skill` command to read the complete up to date skill
tools1,027
simplify
Review changed code for reuse, quality, and efficiency, then fix any issues found. Use when the user wants to clean up, simplify, or review recently changed code. Launches three parallel review agents (code reuse, code quality, efficiency) and aggregates findings.
development1,027
opensrc
Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for", "read the source of", "how does X work internally", "get the implementation of", "opensrc path", or any task requiring access to dependency source code beyond types and docs.
development1,027
lintcn
Type-aware TypeScript lint rules in .lintcn/ Go files. Only load this skill when creating, editing, or debugging rule files. To just run the linter: `npx lintcn lint` (or `--fix`, `--tsconfig <path>`). Finds .lintcn/ by walking up from cwd. First build ~30s, cached ~1s. In monorepos, run from each package folder, not the root. Warnings don't fail CI and only show for git-changed files by default. Use `--all-warnings` to see them across the entire codebase.
development1,027
x-articles
Edit x.com (Twitter) long-form article drafts reliably. Use this for markdown imports, bulk formatting, code blocks, headings, lists, and repeated inline styling. Inspect and validate with Playwriter, but prefer x.com (Twitter) article GraphQL mutations for deterministic updates.
development1,027
errore
errore is Go-style error handling for TypeScript: return errors instead of throwing them. Instead of Go's two-value tuple (val, err), functions return a single Error | T union. Instead of checking err != nil, you check instanceof Error. TypeScript narrows the type automatically — forget to check and your code won't compile. No wrapper types, no Result monads, just unions and instanceof. The errore npm package provides helper utilities (createTaggedError, tryAsync, matchError, findCause, partition) but the core pattern is zero-dependency. Benefits: every error is visible in the return type, callers can't forget to handle errors, flat control flow with early returns instead of nested try-catch, and errors carry typed properties with cause chains for debugging. ALWAYS read this skill when a repo uses the errore "errors as values" convention (errore.org). ALWAYS use errore for new TypeScript projects.
tools1,027
proxyman
Reverse-engineer HTTP APIs using Proxyman for macOS. Intercept, record, and export network traffic from CLI tools and apps (Node.js, Python, Ruby, Go, curl). Export as HAR (JSON) and analyze with jq. Use this skill when the user wants to capture, inspect, or reverse-engineer HTTP traffic from macOS applications.
tools1,027
event-sourcing-state
Event-sourced application state pattern for TypeScript apps. Prefer bounded event logs plus pure derivation functions over mirrored mutable lifecycle flags. Use when state transitions are driven by events and bugs can be reproduced from a saved event stream.
development1,027
zustand-centralized-state
Centralized state management pattern using Zustand vanilla stores. One immutable state atom, functional transitions via setState(), and a single subscribe() for all reactive side effects. Based on Rich Hickey's "Simple Made Easy" principles: prefer values over mutable state, derive instead of cache, centralize transitions, and push side effects to the edges. Resource co-location in the same store is also valid when lifecycle management is safer that way. Also covers state encapsulation: keeping state local to its owner (closures, plugins, factory functions) so it doesn't leak across the app, reducing the blast radius of mutations. Also covers event sourcing: keeping a bounded event buffer and deriving state with pure functions instead of mutable flags, making event handlers easy to test and reason about. Use this skill when building any stateful TypeScript application (servers, extensions, CLIs, relays) to keep state simple, testable, and easy to reason about. ALWAYS read this skill when a project uses zustand/vanilla for state management outside of React.
tools1,027
jitter
Control Jitter (jitter.video) for exporting animations, replacing assets, and modifying text programmatically via Playwriter.
testing1,027
egaki
AI image and video generation CLI. Use this skill to install egaki, configure auth, run help commands, and generate images or videos with provider keys or an Egaki subscription.
tools1,022
critique
Git diff viewer. Renders diffs as web pages, images, and PDFs with syntax highlighting. Use this skill when working with critique for showing diffs, generating diff URLs, or selective hunk staging.
development1,016
tuistory
tmux for AI agents. Run dev servers and TUIs in named background sessions that agents can read, wait on, snapshot, and type into. Replaces tmux with reactive waiting instead of blind `sleep`. Projects wrap their dev script with tuistory (`"dev": "tuistory -- next dev"`) so agents get a background session and humans get auto-attached. Use tuistory when you need to: - Run background dev servers or long-lived processes - Control interactive CLIs and TUIs (type, press keys, click, wait, snapshot) - Write Playwright-style tests for terminal apps **CLI** (`tuistory`) for background sessions. **JS/TS API** (`launchTerminal`) for programmatic control and tests.
tools332
zele
zele is a multi-account email and calendar CLI for Gmail, IMAP/SMTP (Fastmail, Outlook, any provider), and Google Calendar. It reads, searches, sends, replies, forwards, archives, stars, and trashes emails, manages drafts, labels, attachments, and Gmail filters, and creates, updates, and deletes calendar events with RSVP and free/busy support. Output is YAML so commands can be piped through yq and xargs. ALWAYS load this skill when the user asks to check email, read/send messages, reply or forward, archive or trash threads, manage drafts or labels, download attachments, schedule meetings, check their calendar, RSVP to events, or when they run any `zele` command. Load it before writing any code or shell commands that touch zele so you know the correct subcommand structure, the Google vs IMAP feature matrix, the headless login flow, and the agent-specific rules.
tools267
errore
errore is Go-style error handling for TypeScript: return errors instead of throwing them. Instead of Go's two-value tuple (val, err), functions return a single Error | T union. Instead of checking err != nil, you check instanceof Error. TypeScript narrows the type automatically — forget to check and your code won't compile. No wrapper types, no Result monads, just unions and instanceof. The errore npm package provides helper utilities (createTaggedError, tryAsync, matchError, findCause, partition) but the core pattern is zero-dependency. Benefits: every error is visible in the return type, callers can't forget to handle errors, flat control flow with early returns instead of nested try-catch, and errors carry typed properties with cause chains for debugging. ALWAYS read this skill when a repo uses the errore "errors as values" convention (errore.org). ALWAYS use errore for new TypeScript projects.
tools248