Affaan MustafaTrading lead at Jump Trading; ECC 290k+ stars7,200 installs on skills.shAPI Design
REST API design patterns including resource naming.
Use Edge to load the skill api-design from affaan-m/ecc for my task. If Edge is not set up, read getedge.cc/SKILL.md and ask me first.
2 static scans, 0 counted findings.
Edge checks it again each time your agent loads it.
From the affaan-m public repository. Edge did not write or edit this skill.
What it does
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs. Use when designing or reviewing REST endpoints, resource names, status codes, pagination, or versioning.
Why Affaan Mustafa
Compute Trading Lead at Jump Trading. Each fact links its public source.
- Role at Jump Trading
His GitHub bio says Compute Trading Lead at Jump Trading, previously founding The Agentic Desk.
GitHub profile - Hugely starred agent harness repo
ECC has 290k+ GitHub stars.
GitHub repo - Security tool with traction
agentshield has 1.3k+ GitHub stars.
GitHub repo
Public sources, checked Oct 26, 2026.
How it works
- 1Copy
Try for free gives you one prompt.
- 2Paste
Paste it into Claude Code, Codex or Cursor.
- 3Ask
Ask for the outcome. Your agent loads API Design.
Related skills
Provides REST API design standards and best practices for Spring Boot projects. Use when creating or reviewing REST endpoints, DTOs, error handling, pagination, security headers, HATEOAS and architecture patterns.
Use when you need to design, review, or improve REST APIs with Spring Boot — including HTTP methods, resource URIs, status codes, DTOs, versioning, deprecation and sunset headers, content negotiation (JSON and vendor med
Audit an existing or proposed public REST API surface as a checklist-driven design review - resource and URI naming, HTTP method and status-code correctness, field-naming consistency, pagination pattern choice, filtering
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
Implements rate limiting and abuse prevention with per-route policies, IP/user-based limits, sliding windows, safe error responses, and observability. Use when adding "rate limiting", "API protection", "abuse prevention"
RESTful API design guidelines following the Richardson Maturity Model through to Level 3 (HATEOAS) for Ruby on Rails. This skill should be used when designing, building, reviewing, or refactoring REST APIs to ensure prop
No evidence record yet
No measured run with and without this skill yet, so this page makes no performance claim. 2 static scans, 0 counted findings. Security state at 2026-11-17: reviewed. Static scans check the code, not how well the skill works.
State definitionsSkill details
Security scansReviewed
2 static scans, 0 counted findings. Security state at 2026-11-17: reviewed. Edge checks it again each time your agent loads it.
Edge static checks (Edge-run): edge-static/1.0.2. Scope: Static patterns for remote execution, credentials with network sends, obfuscation, prompt overrides, hidden Unicode, binaries and persistence. Raw findings: not supplied.
Edge committed-secret checks (Edge-run): edge-secrets/1.0.0. Scope: Credentials committed in the skill's files (values never shown). Raw findings: not supplied.
Socket (skills.sh mirror): Version unavailable. Scope: Not supplied by the mirrored record. Raw findings: not supplied.
Snyk (skills.sh mirror): Version unavailable. Scope: Not supplied by the mirrored record. Raw findings: not supplied.
- Edge static checks
- Pass · 0 counted findings · 2026-11-17
- Edge committed-secret checks
- Pass · 0 counted findings · 2026-11-17
Creator, source & licenceaffaan-m
From the affaan-m public repository. Edge did not write or edit this skill.
- Repository
- affaan-m/ecc
- Skill file
- View source at revision
- Revision
- d3b8a3e908904e242ed2dbe66af62cca71131419
- Package hash
- sha256:53d7cfdcf1d7985b83b0fc066595cb0839ef40b14173db8b83faa79ab4fb994b
- Licence
- MIT
- Description
- REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs. Use when designing or reviewing REST endpoints, resource names, status codes, pagination, or versioning.
Quoted from the skill’s own description
Read skill files1 file
1 file, 12.9 KB at revision d3b8a3e90890.
Questions about API Design
What does API Design do?
REST API design patterns including resource naming. Published by Affaan Mustafa (affaan-m/ecc).
Is API Design safe to use?
Edge security state: Reviewed (2 Edge-run static scans, scanned Nov 17, 2026). The Evidence tab shows the scan.
How do I use API Design in Claude Code, Codex or Cursor?
Click Try for free, pick your agent and follow its one step. Edge is free, with no Edge account.
Similar skills

A relentless interview to sharpen a plan or design.

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX"…

tasteskill 2.5.1, the anti-slop frontend skill. Builds professional company websites at the level of figma.com and x.ai: plain copy in a voi…

Emil Kowalski's design-engineering philosophy for UI polish, component design, animation decisions, and the invisible details that make soft…

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-design…

Extract design primitives from a public website and generate starter token files for your project.
Design and implement one-click post-purchase upsells and downsells that raise average order value without hurting the main conversion rate.…

Design skill for websites and new pages that look designed, not generated. Use when the user asks to build or design something new, or names…