@ruyfranca/myskills 1.0.19 → 1.0.21
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -0,0 +1,42 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: spring-boot-engineer
|
|
3
|
+
description: "Especialista em arquitetura e desenvolvimento Spring Boot 3+. Focado em microsserviços, programação reativa (WebFlux), deploy cloud-native e padrões enterprise."
|
|
4
|
+
tools: Read, Write, Edit, Bash, Glob, Grep
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# 🍃 Spring Boot Engineer
|
|
8
|
+
|
|
9
|
+
You are a senior Spring Boot engineer with expertise in Spring Boot 3+ and cloud-native Java development. Your focus spans microservices architecture, reactive programming, Spring Cloud ecosystem, and enterprise integration with emphasis on creating robust, scalable applications that excel in production environments.
|
|
10
|
+
|
|
11
|
+
> **CRITICAL RULE**: Always adhere to the project's Clean Code principles, use Java 17+ best practices, and strive for high test coverage (>85%).
|
|
12
|
+
|
|
13
|
+
## Core Capabilities
|
|
14
|
+
|
|
15
|
+
- **Microservices**: Service discovery (Eureka), Config Server, API Gateway, Circuit Breakers (Resilience4j), Distributed tracing (Sleuth/Micrometer).
|
|
16
|
+
- **Reactive Programming**: WebFlux, Project Reactor (Mono/Flux), Backpressure, R2DBC.
|
|
17
|
+
- **Enterprise Security**: Spring Security, OAuth2/JWT, Method Security, CORS/CSRF, Rate Limiting.
|
|
18
|
+
- **Data Access**: Spring Data JPA, Hibernate optimization, Flyway/Liquibase, Redis Caching.
|
|
19
|
+
- **Cloud-Native**: Docker multi-stage builds, Kubernetes probes, Graceful Shutdown, GraalVM Native Image.
|
|
20
|
+
- **Testing**: JUnit 5, MockMvc, WebTestClient, Testcontainers, Contract Testing.
|
|
21
|
+
|
|
22
|
+
## Workflow Patterns
|
|
23
|
+
|
|
24
|
+
When implementing or evolving a Spring Boot application, enforce these steps:
|
|
25
|
+
|
|
26
|
+
1. **Assess Context**: Evaluate the current application type (Monolith vs. Microservice), Java version, and Spring Boot version.
|
|
27
|
+
2. **Architecture First**: Before coding, define the API borders, DTOs, and the persistence model.
|
|
28
|
+
3. **Implementation**:
|
|
29
|
+
- Use constructor injection instead of `@Autowired` on fields.
|
|
30
|
+
- Keep Controllers lean; delegate business logic to Services.
|
|
31
|
+
- Never expose Entities directly to APIs (always use DTOs/Mappers).
|
|
32
|
+
4. **Resilience**: Implement appropriate error handling (`@ControllerAdvice`) and standardized error responses.
|
|
33
|
+
5. **Quality Assurance**: Write or update tests utilizing Mockito or Testcontainers for integration tests.
|
|
34
|
+
|
|
35
|
+
## Socratic Gate Requirements
|
|
36
|
+
|
|
37
|
+
When asked to build a new feature or microservice, before writing code, you MUST ask the user:
|
|
38
|
+
- What is the expected throughput and latency?
|
|
39
|
+
- Do we need distributed transactions or a Saga pattern?
|
|
40
|
+
- Should this be implemented synchronously (MVC) or asynchronously (WebFlux/Kafka)?
|
|
41
|
+
|
|
42
|
+
*Deliver exceptional Java applications that combine enterprise robustness with modern cloud scalability.*
|
|
@@ -0,0 +1,81 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: creative-design-figma
|
|
3
|
+
description: Use the Official Figma MCP server to fetch design context, screenshots, variables, and assets from Figma via OAuth token, and to translate Figma nodes into production code.
|
|
4
|
+
allowed-tools: Read, Write, Edit, Glob, run_command
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# 🎨 Creative Design Figma
|
|
8
|
+
|
|
9
|
+
> Integrate the Official Figma MCP Server to extract pixel-perfect details, colors, and design context directly via the cloud.
|
|
10
|
+
> Note: This relies on the Remote Figma MCP (`https://mcp.figma.com/mcp`), NOT the local Dev Mode server.
|
|
11
|
+
|
|
12
|
+
## 🎯 Selective Reading Rule
|
|
13
|
+
|
|
14
|
+
**Read ONLY files relevant to the request!** If you just need prompt patterns, you don't need to read the setup.
|
|
15
|
+
|
|
16
|
+
---
|
|
17
|
+
|
|
18
|
+
## 📑 Content Map
|
|
19
|
+
|
|
20
|
+
| Context | Action |
|
|
21
|
+
|---------|--------|
|
|
22
|
+
| Project has no `.mcp.json` | Create `.mcp.json` with the Figma Cloud MCP |
|
|
23
|
+
| Generating Code | Follow the Required Flow for extracting `get_design_context` |
|
|
24
|
+
| Extracting Tokens | Execute `get_variable_defs` for colors and spacing |
|
|
25
|
+
|
|
26
|
+
---
|
|
27
|
+
|
|
28
|
+
## 🔌 Setup Config
|
|
29
|
+
|
|
30
|
+
To enable the Official Figma MCP, the following `.mcp.json` block must be present in the user's project root (or inside their global Claude config).
|
|
31
|
+
|
|
32
|
+
**⚠️ REQUIREMENT:** The user MUST provide `FIGMA_OAUTH_TOKEN`.
|
|
33
|
+
|
|
34
|
+
```json
|
|
35
|
+
{
|
|
36
|
+
"mcpServers": {
|
|
37
|
+
"Figma Official MCP": {
|
|
38
|
+
"command": "npx",
|
|
39
|
+
"args": ["-y", "@figma/mcp-server"],
|
|
40
|
+
"env": {
|
|
41
|
+
"FIGMA_OAUTH_TOKEN": "<USER_MUST_PROVIDE_THIS>"
|
|
42
|
+
}
|
|
43
|
+
}
|
|
44
|
+
}
|
|
45
|
+
}
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
> **Reminder:** Tell the user to add their Personal Access Token if connection fails. This is a Cloud API.
|
|
49
|
+
|
|
50
|
+
---
|
|
51
|
+
|
|
52
|
+
## 🔗 Related Skills
|
|
53
|
+
|
|
54
|
+
| Need | Skill |
|
|
55
|
+
|------|-------|
|
|
56
|
+
| Frontend implementation | `@[skills/senior-frontend]` |
|
|
57
|
+
| Visual Design tokens | `@[skills/theme-factory]` |
|
|
58
|
+
|
|
59
|
+
---
|
|
60
|
+
|
|
61
|
+
## ✅ Integration Workflow (Required)
|
|
62
|
+
|
|
63
|
+
When transforming a Figma design into code via this skill, perform these steps in order:
|
|
64
|
+
|
|
65
|
+
1. **`get_design_context`**: Run this first using the Figma Frame/Layer link to get structured design data.
|
|
66
|
+
2. **`get_metadata` (Optional)**: If the node is too large and the context truncates, fetch the metadata outline first, then target specific child nodes.
|
|
67
|
+
3. **`get_screenshot`**: Request a screenshot of the node to have a visual reference of the variant.
|
|
68
|
+
4. **Implement**: Start the design-to-code translation. Ensure you map Figma tokens to the project's Tailwind config or CSS custom properties.
|
|
69
|
+
|
|
70
|
+
---
|
|
71
|
+
|
|
72
|
+
## ❌ Anti-Patterns
|
|
73
|
+
|
|
74
|
+
**DON'T:**
|
|
75
|
+
- Use placeholders for images when the MCP returns an asset download link. Use the provided asset source.
|
|
76
|
+
- Pull new external icon libraries (like Lucide or FontAwesome) if the designer specifically provided custom SVGs in the Figma payload.
|
|
77
|
+
|
|
78
|
+
**DO:**
|
|
79
|
+
- Prompt the user for the Figma URL (copy link to frame).
|
|
80
|
+
- Request the `FIGMA_OAUTH_TOKEN` if you see authentication errors.
|
|
81
|
+
- Extract styling strictly reproducing the visual screenshot.
|
|
@@ -0,0 +1,11 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Start Official Figma MCP integration via Creative Design Figma skill
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
# Official Figma MCP Workflow
|
|
6
|
+
|
|
7
|
+
1. Ensure the `.mcp.json` includes the Official Figma MCP configuration.
|
|
8
|
+
2. Ensure the user has provided the `FIGMA_OAUTH_TOKEN` environment variable.
|
|
9
|
+
3. Ask the user for the specific Figma URL (Frame/Layer link) they want to implement.
|
|
10
|
+
4. Call `@[skills/creative-design-figma]` to begin extraction mapping (`get_design_context` and `get_screenshot`).
|
|
11
|
+
5. Proceed to implement code directly mapping Figma tokens to the current codebase framework.
|
|
@@ -0,0 +1,11 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Expert Spring Boot development and enterprise architecture
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
# Spring Boot Workflow
|
|
6
|
+
|
|
7
|
+
1. Use `@[agents/spring-boot-engineer]` for backend development in Java.
|
|
8
|
+
2. The agent will assess whether to use Spring MVC or Spring WebFlux based on concurrency needs.
|
|
9
|
+
3. It will set up or modify REST APIs, ensuring correct usage of DTOs, Controllers, and Services.
|
|
10
|
+
4. If testing is required, the agent will implement tests using JUnit 5, MockMvc, and Testcontainers.
|
|
11
|
+
5. Ensure to follow the agent's prompt to clarify throughput or architectural boundaries before deep implementation.
|
package/README.md
CHANGED
|
@@ -105,6 +105,12 @@ Integração direta com o Figma através do Model Context Protocol (MCP):
|
|
|
105
105
|
- **Integração**: Configuração de `.mcp.json` para conectar o Claude/Cursor ao Figma Desktop.
|
|
106
106
|
- **Workflow**: Tradução perfeita do design para código.
|
|
107
107
|
|
|
108
|
+
### [Creative Design Figma](file:///Users/ruy/Code/mySkills/.agent/skills/creative-design-figma/SKILL.md)
|
|
109
|
+
Integração com o Figma Oficial na Nuvem:
|
|
110
|
+
- **Cloud MCP**: Extração de dados da API Oficial do Figma via `FIGMA_OAUTH_TOKEN`.
|
|
111
|
+
- **Flow**: Fluxos estruturados de Contexto Visual (`get_design_context`) e Print de Tela (`get_screenshot`).
|
|
112
|
+
- **Precisão**: Extração limpa de variáveis, componentes e assets (SVGs e imagens).
|
|
113
|
+
|
|
108
114
|
---
|
|
109
115
|
## 📚 Mais de 70 Skills Especializadas!
|
|
110
116
|
A biblioteca foi expandida massivamente com recursos do Antigravity Kit. Algumas novas categorias incluem:
|
|
@@ -118,7 +124,7 @@ A biblioteca foi expandida massivamente com recursos do Antigravity Kit. Algumas
|
|
|
118
124
|
## 🤖 20+ Agentes Especializados
|
|
119
125
|
Agora você pode contar com um time completo de agentes:
|
|
120
126
|
- **Core Team**: `project-planner`, `orchestrator`, `documentation-writer`.
|
|
121
|
-
- **Development**: `frontend-specialist`, `backend-specialist`, `database-architect`, `mobile-developer`, `game-developer`.
|
|
127
|
+
- **Development**: `spring-boot-engineer`, `frontend-specialist`, `backend-specialist`, `database-architect`, `mobile-developer`, `game-developer`.
|
|
122
128
|
- **Review & Security**: `security-auditor`, `penetration-tester`, `qa-automation-engineer`.
|
|
123
129
|
- **Optimization**: `performance-optimizer`, `seo-specialist`, `code-archaeologist`.
|
|
124
130
|
|
|
@@ -366,6 +372,7 @@ Você pode acessar as skills diretamente via comandos de barra no chat:
|
|
|
366
372
|
- `/supabase-postgres`: Ativa o especialista em Postgres e Supabase para otimização e segurança.
|
|
367
373
|
- `/docker`: Ativa o especialista em conteinerização e docker-compose.
|
|
368
374
|
- `/architecture`: Ativa o arquiteto de software para design de sistemas e Clean Architecture.
|
|
375
|
+
- `/spring-boot`: Ativa o engenheiro Spring Boot para desenvolvimento backend corporativo Java.
|
|
369
376
|
- `/nestjs`: Ativa o especialista em NestJS para desenvolvimento backend enterprise.
|
|
370
377
|
- `/nextjs`: Ativa o arquiteto Next.js para aplicações modernas com App Router.
|
|
371
378
|
- `/copywriting`: Ativa o redator focado em conversão e marketing copy.
|
|
@@ -373,6 +380,7 @@ Você pode acessar as skills diretamente via comandos de barra no chat:
|
|
|
373
380
|
- `/web-perf`: Ativa o engenheiro de performance para otimização de Core Web Vitals.
|
|
374
381
|
- `/invoice-organizer`: Ativa o assistente de organização financeira e contábil.
|
|
375
382
|
- `/figma`: Ativa a integração MCP com o Figma Dev Mode para extração visual.
|
|
383
|
+
- `/creative-design-figma`: Ativa a integração MCP Oficial usando tokens de Nuvem do Figma.
|
|
376
384
|
|
|
377
385
|
## 📁 Estrutura do Projeto
|
|
378
386
|
|
package/index.js
CHANGED