agentleFS
0xSoftBoi0xSoftBoi/suwappubot/.claude/skills/goal/SKILL.md

goal

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Standing goal: connect every built-but-unwired feature. Shows the audited disconnect backlog (Jul 2026), how to verify each item, and how to keep this list current. Usage: /goal [item]

50 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use origin, update-cli-config 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.
  • 0mlkrizzz655335vSkill

    origin

    origin CLI 管理。安装、登录、更新、修复 origin.cursor.com 的 CLI。"disabled-environments:

    Also in 3 projects that use this

  • PandelisZSkill

    update-cli-config

    View and modify Cursor CLI configuration settings in ~/.cursor/cli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.

    Also in 4 projects that use this

  • 0mlkrizzz655335vSkill

    review-bugbot

    缺陷导向代码审查。用 Bugbot 子代理找 bug。

    Also in 3 projects that use this

  • 32103210Skill

    migrate-to-skills

    Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills format (.cursor/skills/). Use when you want to migrate rules or commands to skills, convert .mdc rules to SKILL.md format, or consolidate commands into the skills directory.

    Also in 4 projects that use this

  • 32103210Skill

    update-cursor-settings

    Modify Cursor/VSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.

    Also in 4 projects that use this

  • MicrosoftSkill

    automate

    Propose an automation from a completed task or a new idea, then create it after approval. Use when the user asks to create an automation or wants scheduled local or cloud agent work.

    Also in 4 projects that use this

  • +3 more from 0mlkrizzz655335v
  • +1 more from 32103210

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 46 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When you find a NEW built-but-unwired feature anywhere, ADD it here.

    line 13
  2. Very specific:

    All wrapped in broad except Exception returning defaults, so they "work" but lie.

    line 18

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

/goal — Connect the scattered features

Standing goal: no feature should exist in the codebase without being wired end-to-end (handler registered, service started, table created, endpoint mounted, UI calling a real backend). This backlog comes from a 3-surface audit (bot / APIs / frontends) on 2026-07-24, triggered by finding the entire support-ticket system built but unregistered (fixed in PR #615) and mobile referral stats returning hardcoded zeros from a nonexistent-method call (same PR).

How to use

  • /goal — review this list, verify the next unchecked item against current code (items may have been fixed since the audit — always re-verify before working), fix it, then check it off and commit the edit to this file.
  • /goal <item> — jump to that item.
  • When you find a NEW built-but-unwired feature anywhere, ADD it here.

The backlog

A. Mobile API ghost methods (api/routes/mobile.py) — silent fake data

All wrapped in broad except Exception returning defaults, so they "work" but lie.

  • A1. mobile.py:552 — await points_service.daily_checkin() is a sync method being awaited → TypeError swallowed; mobile daily check-in never credits points. Fix: call sync, map response.
  • A2. mobile.py:565 — points_service.get_milestones() does not exist. Find the real milestones source (points_service) and wire it.
  • A3. mobile.py:600 — points_service.redeem_reward() does not exist (real: redeem_subscription_reward / redeem_marketplace_reward). Mobile redemption silently no-ops. MONEY-PATH — tag reviewer.
  • A4. mobile.py:692 — referral_service.get_stats() → fixed in PR #615 (get_referral_stats, key mapping).
  • A5. Sweep done (remaining awaits are legitimately async: ws.create_wallet, httpx calls). Tests for api/routes/mobile.py still missing — [SUW-200]. Sweep the REST of mobile.py for the same pattern (every await <service>.<method> inside try/except: verify the method exists and its sync/async-ness). Add tests for api/routes/mobile.py — currently zero coverage.

B. Bot: unstarted services & orphaned models

  • B1. Support system (handlers + notifier + SupportTicket model) — wired in PR #615.
  • B2. Wired: battle_monitor start/stop in bot/main.py (settles expired /battle positions). bot/services/battle_monitor.py
  • B3. Fixed: imports added to database/db.py. Models never imported in database/db.py schema init (tables may never be created — verify at runtime first; another import path may create them): bot/models/custodial.py (CustodialBalance, CustodialTransaction, HotWallet, GasSponsorshipConfig, UserGasUsage), bot/models/favorites.py (FavoriteSwapPair, PriceAlert, UserSettings), bot/models/tempo_access_key.py.

C. Unmounted / missing API routes

  • C1. Mounted at /webapp/tokens in app.ts. api-ts/src/routes/tokens.ts exports tokenRoutes but is never mounted in app.ts (intended /webapp/tokens per its comments) → webapp's /webapp/tokens/prices call (api.ts:322) has no backend.
  • C2. Deleted all three stale try/except blocks (functionality already mounted via api/webapp.py + inline agent routes). api/main.py:653,660,667 — imports api.routes.webapp, api.routes.swap, api.routes.a2a which don't exist as files; silently skipped by try/except. Decide: create, repoint, or remove the imports.
  • C3. Added GET /webapp/tokens/lookup to api-ts (Li.Fi-backed; safetyScore=null until a real scorer is plumbed — UI shows "Unknown"). Was: webapp calls /webapp/tokens/lookup (webapp/src/lib/api.ts:868) which does not exist in api-ts tokens.ts — add or repoint.

D. Frontend calls with no (or wrong-path) backend

  • D1. Webapp support form called /webapp/support/tickets with NO backend in either stack (the June api-ts routes were wiped). Fixed in PR #615: GET/POST /webapp/support/tickets added to Python api/webapp.py (terminal-JWT auth, support_notifier fan-out picks tickets up via notified_at).
  • D2. [SUW-194] /webapp/snipe POST (api.ts:634) — no backend in either stack; webapp snipe is dead. MONEY-PATH when built.
  • D3. Added GET /webapp/users/me/swaps/{id} (user-scoped, 404-not-403) + repointed webapp client. GET /swaps/{id} (api.ts:122) — no detail endpoint in either stack.
  • D4. Triaged: panel is correctly gated (COMING_SOON flag, no 404s reach users); account CRUD endpoints live in api/webapp.py:2037-2103; only the feed is a [] stub (api/webapp.py:2131) pending a tweet provider decision (Twitter API vs scraper) — product call, moved to F. Terminal tweet monitor (terminal/src/components/tweets/TweetMonitorPanel.tsx) — all /webapp/tweets/* calls 404; no backend.

E. "Coming soon" stubs where the backend already EXISTS (quick wins)

  • E1. Gate removed; panel wired to existing /webapp/alerts. Terminal AlertsPanel (terminal/src/components/alerts/AlertsPanel.tsx:30,56) — disabled stub, but /webapp/alerts backend exists. Wire it.
  • E2. DCAPanel rewritten onto real useDCA hook (/webapp/dca/orders); DCAManager gate removed. Terminal DCAPanel (terminal/src/components/trade/DCAPanel.tsx:68-73) — stub, DCA backend exists (mobile/bot paths). Wire it.

F. Genuine not-yet-built stubs (product decisions, not wiring)

  • F0. [SUW-195] Tweet feed provider for terminal tweet monitor (see D4) — pick Twitter API vs scraper, implement feed at api/webapp.py:2131, flip COMING_SOON.
  • F1. [SUW-196] Webapp Wallet "Send funds" (Wallet.tsx:350) — alert('coming soon'). Terminal has deposit/withdraw; port it.
  • F2. [SUW-197] Terminal perps TP/SL (PositionsTable.tsx:33,276) — needs backend order-type support.
  • F3. [SUW-198] P2P native escrow (P2P.tsx:213,384) — executor unwired (EscrowNotConfiguredError; known).
  • F4. [SUW-199] Webapp in-app referral claiming (Referrals.tsx:216) — intentional bot-only for now.
  • F5. [SUW-224] Jelly-native social discovery and creator claim — implementation is mounted in api/main.py beneath the already-live /webapp Python prefix and rendered at protected Webapp /discover through the Home Social Pulse entry point. Claim proof accepts only a canonical https://jellyjelly.com/watch/{id} URL, verifies a short-lived recorded public phrase, ties it to a wallet-backed session, and stores only source metadata (never video/HLS/MP4). Contract: tests/test_social_routes.py. Verified live on 2026-08-08: Railway deployed both the API and webapp, and api.suwappu.bot/webapp/social/jellies returned safe canonical source metadata.

Rules

  • Re-verify every claim against current code before acting — this is a point-in-time audit.
  • Anything touching funds/points/keys: tag MONEY-PATH and get money-path-reviewer before merge.
  • The disease pattern to grep for elsewhere: broad except Exception returning defaults around service calls; exported handlers not in bot/main.py; .start() services never started; Hono routers never .route()d; frontend paths not in either stack.

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.