agentleFS
Sign inStart free
kartikkabadikartikkabadi/synara-beta/.claude/skills/verify/SKILL.md

verify

Skill6 starsChanged 2 months agoMITView on GitHub

How to launch an isolated Synara instance (server + web) to observe UI changes, without touching ~/.synara or the default dev ports. Then open http://localhost:5899/. Chrome extension may be unavailable; playwright is a devDependency of apps/web — import it by absolute path from apps/web/node_modules/playwright/index.mjs in a scratch script.

188 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use instinct-export, instinct-import and 10 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.
  • TheKREATORSSkill

    instinct-export

    Export instincts from project/global scope to a file

    Also in 3 projects that use this

  • TheKREATORSSkill

    instinct-import

    Import instincts from file or URL into project/global scope

    Also in 3 projects that use this

  • AviadPSkill

    risk-assess

    Assess the risk and blast radius of a proposed code change before implementing it. Evaluates CI impact, framework-wide vs localized scope, rollback path, and identifies blindspots. Use when user says "what's the risk", "is this safe", "assess the impact", "risk assess", "blast radius", or before applying framework-wide or CI-affecting changes. Do NOT use for code quality review (use code-quality) or plan validation (use design-validator).

    Also in 3 projects that use this

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 6 projects that use this

  • AaravChadhaSkill

    secure

    Security review with a confidence gate - a finding exists only with a concrete exploit scenario and a high/medium/low confidence rating; everything else goes to a worth-hardening list, never inflated. Sweeps five surfaces: auth gates, secrets hygiene, injection and unsafe sinks, unsafe deserialization/crypto/transport, and LLM tool-use trust boundaries. Reports only, never fixes. Use when the user asks for a security review or to check vulnerabilities, secrets, or auth.

    Also in 3 projects that use this

  • ArvorCoSkill

    specify

    Create feature specification from natural language description. Use when starting a new feature or creating a spec. Triggers on: create spec, specify feature, new feature spec.

    Also in 10 projects that use this

  • +1 more from TheKREATORS

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Default ports are 3773 (server) / 5733 (web) plus a per-checkout hash offset — pick explicit distinct ports to avoid colliding with a …

    line 24

“Common” is measured: kept by at least 6 in 10 of the 167 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Verify: run Synara locally for runtime verification

How to launch an isolated Synara instance (server + web) to observe UI changes, without touching ~/.synara or the default dev ports.

Launch

# 1. Server (from the directory you want as the workspace/project cwd):
SYNARA_HOME=<scratch>/synara-home \
SYNARA_PORT=3899 SYNARA_MODE=web SYNARA_NO_BROWSER=1 \
VITE_DEV_SERVER_URL=http://localhost:5899 \
bun <repo>/apps/server/src/index.ts &

# 2. Web (vite dev):
cd <repo>/apps/web && PORT=5899 VITE_WS_URL=ws://localhost:3899 bun run dev &

Then open http://localhost:5899/.

Gotchas

  • VITE_DEV_SERVER_URL on the server is required — without it the WS handshake from the vite origin is rejected with 403 (see apps/server/src/trustedOrigins.ts).
  • VITE_WS_URL on the web side tells the app where the WS server lives (apps/web/src/wsTransport.ts).
  • Default ports are 3773 (server) / 5733 (web) plus a per-checkout hash offset — pick explicit distinct ports to avoid colliding with a running dev instance.
  • The project picker ("Work in a project") only lists top-level folders in $HOME and clicking one selects it as the workspace immediately (no drill-down). To open a test repo, place/symlink it at ~/<name> temporarily.
  • To see diffs: select a git workspace with uncommitted changes, then click the +N −N toggle in the top-right chat header — it opens the DiffPanel (working-tree diff). No project/thread needed.
  • Server tests: don't run the suite from a checkout under /private/tmp — localImageRoute.test.ts fails there (its "outside the workspace" fixture lands in an allowed temp root). It passes from a normal checkout and on CI.

Playwright driving

Chrome extension may be unavailable; playwright is a devDependency of apps/web — import it by absolute path from apps/web/node_modules/playwright/index.mjs in a scratch script.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free