en un clic
sn-mcp-server
sn-mcp-server contient 6 skills collectées depuis signnow, avec une couverture métier par dépôt et des pages de détail sur le site.
Skills dans ce dépôt
Use when preparing to commit changes or drafting a git commit message in this repo.
SignNow MCP Server architecture rules, layer constraints, and design philosophy. Use when working on any source code in this project — implementing features, reviewing code, writing specs, planning, or testing. Covers the Thin Translator philosophy, stateless design, layer access matrix, dependency rules, and known gotchas. Do NOT use for git commits or documentation-only tasks.
Coding standards and implementation patterns for SignNow MCP Server. Use when writing or modifying Python source code in this project — implementing features, fixing bugs, refactoring. Covers layer-specific coding rules, error handling patterns, typing standards, the bug fix protocol, and verification steps. Do NOT use for spec writing, planning, or test authoring — those have dedicated skills.
Convert technical specifications into step-by-step implementation plans for SignNow MCP Server. Use when creating an execution plan, breaking down a spec into tasks, or organizing implementation work into phases. Covers phase structure, layer tags, constraint checks, and the plan output format. Do NOT use for writing specs, implementing code, or writing tests.
Write technical specifications for SignNow MCP Server features. Use when designing a new feature, writing a spec, performing architecture review, or converting a feature idea into requirements. Covers the analysis protocol (philosophy check, layer check, tool design, auth, errors, testability), spec output format, and Pydantic model design. Do NOT use for implementation, testing, or planning — those have dedicated skills.
Testing strategy and conventions for SignNow MCP Server. Use when writing, reviewing, or modifying unit tests in this project. Covers per-layer testing patterns, mocking conventions (MagicMock for SignNowAPIClient, AsyncMock for Context), async test handling, parametrize usage, the analyze protocol (3 YES criteria), and verification steps. Do NOT use for implementation, spec writing, or planning.