Expert guidance for designing scalable APIs, microservices, and distributed backend systems.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add sickn33/antigravity-awesome-skills --skill backend-architectCompatible with
Supported agents
Covers API design patterns (REST, GraphQL, gRPC, WebSockets), service boundaries using domain-driven design, and inter-service communication strategies (synchronous and asynchronous)
Includes resilience patterns (circuit breakers, retries, timeouts), observability architecture (logging, metrics, distributed tracing), and security patterns (OAuth, JWT, RBAC, rate limiting)
Provides event-drive
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionbackend-architectExecute the skills CLI command in your project's root directory to begin installation:
epx add sickn33/antigravity-awesome-skills --skill backend-architectFetches backend-architect from sickn33/antigravity-awesome-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/backend-architect
Restart Cursor to activate backend-architect. Access via /backend-architectin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
discord-bot-architect
sickn33/antigravity-awesome-skills · Productivity · same repo
typescript-advanced-types
sickn33/antigravity-awesome-skills · Backend · same repo
react-native-architecture
sickn33/antigravity-awesome-skills · Frontend · same repo
cpp-pro
sickn33/antigravity-awesome-skills · Productivity · same repo
backend-development
mrgoonie/claudekit-skills · Backend · tag: backend
golang-architect
tomlord1122/tomtom-skill · Backend · tag: architect
Solid pick for teams standardizing on skills: backend-architect is focused, and the summary matches what you get after install.
backend-architect has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in backend-architect — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend backend-architect for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in backend-architect — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
backend-architect fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
backend-architect reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend backend-architect for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
backend-architect reduced setup friction for our internal harness; good balance of opinion and flexibility.
backend-architect has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 26