主机
自建中转要出站 IP?上 LisaHost。
家宽 / 住宅 IP,官网有 CN2 GIA。自己搭中转、跑 MCP。现价看官网。
主机
家宽 / 住宅 IP,官网有 CN2 GIA。自己搭中转、跑 MCP。现价看官网。
支付
美国虚拟卡、Claude / ChatGPT 礼品卡、卡台自助。开完卡继续写代码。
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when executing implementation plans with independent tasks in the current session
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Browser agents and stealth cloud browsers for AI: run web tasks, fill forms, extract data.
Real-time global intelligence across conflict, markets, energy, trade, shipping and cyber. 95 tools.
Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.
Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.
AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.
Review frontend code and live pages against 386 quality-gated web development rules.
Up-to-date docs for AI agents
MCP server for Chrome DevTools
Draw and visually collaborate with your agents on tldraw's canvas.
Lets AI clients search, explore, query, and visualize data in a Metabase instance.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Add or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.
Add or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.
Check a GitHub, GitLab, or Perforce PR/MR/CL for review comments, failing checks, and PR-body gaps. Use when asked to inspect, fix, or prepare a change for submission.
Create agent company packages that conform to agentcompanies/v1. Use when asked to create a company, scaffold an agent team, hire agents, or turn a repo/skills collection into a company package.
Create or modify Paperclip agent adapters across server, UI, and CLI surfaces. Use when adding support for a new CLI agent, API agent, custom process, or adapter package.
Create and kick off a Paperclip case from a user request, with workflow instructions and an initial agent.
- Build and qualify external bots such as Dot in Paperclip. Use for two-way work, invitation, identity, wakeup, Runner lifecycle, native tools, recovery, and Cloud delivery. CLI adapters and app-only connectors use their existing skills.
Add a new Paperclip issue-thread interaction kind end-to-end. Use when repo work introduces or extends interaction cards like request_confirmation, checkbox confirmations, ask_user_questions, or suggest_tasks.
Turn an idea, tweet, or task into a skill in the Paperclip skills catalog (packages/skills-catalog). Use when asked to FIND or MAKE a skill and publish it as a bundled/optional catalog skill: research prior art, reference or author it, add examples, regenerate the manifest, open a PR.
Add a new harness/provider integration to native Paperclip Runner, from requirements and protocol research through implementation, packaging, and real end-to-end acceptance. Use for new Runner adapters; legacy direct adapter authoring and migration are outside this skill.
Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, \"make a control skill for this repo\", or when a project has no scripted way to prove UI/CLI/service behavior.
Handle confidential GitHub Security Advisory response for Paperclip. Use when coordinating advisory triage, private-fork fixes, CVE/publication steps, and immediate security releases.