create-yss-spec 1.1.4 → 2.0.0

package/template/.agents/skills/code-review/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: code-review
-description: Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
+description: Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/Spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
 ---
 
 Two-axis review of the diff between `HEAD` and a fixed point the user supplies:
 
 - **Standards** — does the code conform to this repo's documented coding standards?
-- **Spec** — does the code faithfully implement the originating issue / PRD / spec?
+- **Spec** — does the code faithfully implement the originating Ticket / Spec?
 
 Both axes run as **parallel sub-agents** so they don't pollute each other's context, then this skill aggregates their findings.
 
@@ -26,9 +26,9 @@ Before going further, confirm the fixed point resolves (`git rev-parse <fixed-po
 
 Look for the originating spec, in this order:
 
-1. Issue references in the commit messages (`#123`, `Closes #45`, GitLab `!67`, etc.) — fetch via the workflow in `docs/agents/issue-tracker.md`.
+1. Ticket references in the commit messages (`#123`, `Closes #45`, GitLab `!67`, etc.) — fetch via the workflow in `docs/agents/issue-tracker.md`.
 2. A path the user passed as an argument.
-3. A PRD/spec file under `docs/`, `specs/`, or `.scratch/` matching the branch name or feature.
+3. A Spec file under `docs/`, `specs/`, or `.scratch/` matching the branch name or feature.
 4. If nothing is found, ask the user where the spec is. If they say there isn't one, the **Spec** sub-agent will skip and report "no spec available".
 
 ### 3. Identify the standards sources

package/template/.agents/skills/code-review/agents/openai.yaml

@@ -0,0 +1,3 @@
+interface:
+  display_name: "Code Review"
+  short_description: "Review a diff on standards and spec"

package/template/.agents/skills/codebase-design/agents/openai.yaml

@@ -0,0 +1,3 @@
+interface:
+  display_name: "Codebase Design"
+  short_description: "Vocabulary for deep-module design"

package/template/.agents/skills/competitive-intelligence/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: competitive-intelligence
-description: Use when researching competitors, market positioning, pricing, feature gaps, customer sentiment, or category trends before Discovery, PRD, product strategy, or roadmap decisions.
+description: Use when researching competitors, market positioning, pricing, feature gaps, customer sentiment, or category trends before Discovery, Spec, product strategy, or roadmap decisions.
 ---
 
 # Competitive Intelligence
 
 Source requested for this project: `anthropics/knowledge-work-plugins`, `sales/skills/competitive-intelligence`.
 
-Use this skill when competitive or market facts are needed to shape product Discovery, PRD scope, positioning, differentiation, pricing assumptions, or roadmap tradeoffs.
+Use this skill when competitive or market facts are needed to shape product Discovery, Spec scope, positioning, differentiation, pricing assumptions, or roadmap tradeoffs.
 
 ## Core Rules
 
@@ -43,11 +43,11 @@ Use this skill when competitive or market facts are needed to shape product Disc
    - Differentiators and defensibility.
    - Gaps and underserved jobs-to-be-done.
    - Risks if we copy the competitor too closely.
-   - Product opportunities for PRD or roadmap.
+   - Product opportunities for Spec or roadmap.
 5. Hand off to lifecycle assets:
    - Update Discovery findings in `docs/discovery/`.
    - Create or update a competitor matrix in `docs/discovery/reports/`.
-   - Feed stable user, pain, MVP, non-goal, and success criteria into `grill-with-docs` and `to-prd`.
+   - Feed stable user, pain, MVP, non-goal, and success criteria into `grill-with-docs` and `to-spec`.
    - Record uncertain claims as assumptions, not requirements.
 
 ## Output Shape
@@ -76,7 +76,7 @@ For a quick brief:
 | 维度 | 竞品 A | 竞品 B | 我们的机会 |
 |---|---|---|---|
 
-### PRD 输入
+### Spec 输入
 - 用户 / 痛点：
 - MVP 建议：
 - 非目标范围：

package/template/.agents/skills/diagnosing-bugs/agents/openai.yaml

@@ -0,0 +1,3 @@
+interface:
+  display_name: "Diagnosing Bugs"
+  short_description: "Diagnose hard bugs and regressions"

package/template/.agents/skills/domain-modeling/agents/openai.yaml

@@ -0,0 +1,3 @@
+interface:
+  display_name: "Domain Modeling"
+  short_description: "Build and sharpen a domain model"

package/template/.agents/skills/excalidraw-diagram-generator/SKILL.md

@@ -33,14 +33,14 @@ Use this skill when users request:
 
 ## YSS Lifecycle Integration
 
-In YSS projects, this skill is a visualization and review aid. It can clarify lifecycle artifacts, but it must not replace Discovery, PRD, OpenAPI, ADR, Spec Delta design, or tests.
+In YSS projects, this skill is a visualization and review aid. It can clarify lifecycle artifacts, but it must not replace Discovery, Spec, OpenAPI, ADR, Spec Delta design, or tests.
 
 Use it after the relevant source artifact exists:
 
 | Lifecycle artifact | Typical timing | Useful diagrams | Recommended output |
 |--------------------|----------------|-----------------|--------------------|
 | Business architecture | Opportunity exploration / Discovery | user journey, value stream, swimlane, capability map, ecosystem map | `docs/discovery/diagrams/` or `docs/architecture/diagrams/` |
-| Functional architecture | PRD baseline / product design / PRD calibration | feature map, module map, dependency graph, page map | `docs/design/diagrams/` or `docs/architecture/diagrams/` |
+| Functional architecture | Spec baseline / product design / Spec calibration | feature map, module map, dependency graph, page map | `docs/design/diagrams/` or `docs/architecture/diagrams/` |
 | System architecture | Engineering baseline / Architecture / Spec Delta design | C4/container view, deployment, sequence, DDD boundary, DFD | `docs/architecture/diagrams/` |
 | Data architecture | Detailed design before persistence / repository work | ER, class, meta-model, lineage graph, query/data-flow diagram | `docs/architecture/diagrams/` |
 
@@ -48,7 +48,7 @@ Guardrails:
 
 - Do not invent product requirements or architecture decisions only from the diagram prompt.
 - Reference the source artifact in the Markdown document that links the `.excalidraw` file.
-- If a diagram exposes a missing field, unclear state, dependency, or boundary problem, write that finding back to the source PRD, OpenAPI Draft, architecture document, ADR, Spec Delta design, or issue.
+- If a diagram exposes a missing field, unclear state, dependency, or boundary problem, write that finding back to the source Spec, OpenAPI Draft, architecture document, ADR, Spec Delta design, or issue.
 - Do not require diagrams for small copy, style, configuration, or single-point bug fixes.
 - For data modeling, metadata management, model versioning, or lineage-analysis products, prefer ER, class/meta-model, DFD, and lineage diagrams before persistence implementation.
 

package/template/.agents/skills/grill-me/agents/openai.yaml

@@ -0,0 +1,5 @@
+interface:
+  display_name: "Grill Me"
+  short_description: "Sharpen a plan through interview"
+policy:
+  allow_implicit_invocation: false

package/template/.agents/skills/grill-with-docs/agents/openai.yaml

@@ -0,0 +1,5 @@
+interface:
+  display_name: "Grill with Docs"
+  short_description: "Grill a design and write its docs"
+policy:
+  allow_implicit_invocation: false

package/template/.agents/skills/grilling/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: grilling
-description: Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
+description: Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
 ---
 
-Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
+Interview me relentlessly about every aspect of this until we reach a shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
 
 Ask the questions one at a time, waiting for feedback on each question before continuing. Asking multiple questions at once is bewildering.
 
-If a *fact* can be found by exploring the codebase, look it up rather than asking me. The *decisions*, though, are mine — put each one to me and wait for my answer.
+If a *fact* can be found by exploring the environment (filesystem, tools, etc.), look it up rather than asking me. The *decisions*, though, are mine — put each one to me and wait for my answer.
 
-Do not enact the plan until I confirm we have reached a shared understanding.
+Do not act on it until I confirm we have reached a shared understanding.

package/template/.agents/skills/grilling/agents/openai.yaml

@@ -0,0 +1,3 @@
+interface:
+  display_name: "Grilling"
+  short_description: "Stress-test thinking one question at a time"

package/template/.agents/skills/handoff/SKILL.md

@@ -9,7 +9,7 @@ Write a handoff document summarising the current conversation so a fresh agent c
 
 Include a "suggested skills" section in the document, which suggests skills that the agent should invoke.
 
-Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
+Do not duplicate content already captured in other artifacts (specs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
 
 Redact any sensitive information, such as API keys, passwords, or personally identifiable information.
 

package/template/.agents/skills/handoff/agents/openai.yaml

@@ -0,0 +1,5 @@
+interface:
+  display_name: "Handoff"
+  short_description: "Compact a conversation into a handoff"
+policy:
+  allow_implicit_invocation: false

package/template/.agents/skills/high-fidelity-html-prototype/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: high-fidelity-html-prototype
-description: Use after low-fidelity prototype review is approved and before PRD calibration, requirement freeze, OpenAPI Draft, or UI implementation when a user-facing YSS feature needs a high-fidelity interactive HTML prototype using Ant Design v6.
+description: Use after low-fidelity prototype review is approved and before Spec calibration, requirement freeze, OpenAPI Draft, or UI implementation when a user-facing YSS feature needs a high-fidelity interactive HTML prototype using Ant Design v6.
 ---
 
 # High Fidelity HTML Prototype
@@ -9,7 +9,7 @@ Use this skill only after `prototype-review` approves the low-fidelity prototype
 
 ## Required Inputs
 
-- PRD baseline: `docs/requirements/<feature>-prd.md`.
+- Spec baseline: `docs/requirements/<feature>-spec.md`.
 - Product overview design / functional architecture: `docs/design/<feature>-product-overview-design.md`.
 - Interaction spec: `docs/design/<feature>-interaction-spec.md`.
 - State matrix: `docs/design/<feature>-state-matrix.md`.
@@ -47,7 +47,7 @@ Use the latest verified v6.x version instead of `6.5.0` when npm reports a newer
 - Prefer Ant Design components and tokens over hand-built controls: `Layout`, `Menu`, `Breadcrumb`, `Button`, `Input`, `Select`, `Table`, `Form`, `Tabs`, `Steps`, `Drawer`, `Modal`, `Alert`, `Tooltip`, `Tag`, `Badge`, `DatePicker`, `Upload`, `Pagination`, `Empty`, `Spin`, `Result`.
 - Do not create extra data-service or fixture artifacts. Use embedded sample data inside the HTML/JS for visual and interaction demonstration only.
 - Mark the file clearly as `PROTOTYPE ONLY - NOT PRODUCTION CODE`.
-- Do not treat the HTML prototype as a stable frontend implementation, generated-client contract, or OpenAPI source of truth. It informs PRD calibration and OpenAPI Draft.
+- Do not treat the HTML prototype as a stable frontend implementation, generated-client contract, or OpenAPI source of truth. It informs Spec calibration and OpenAPI Draft.
 
 ## Interaction Coverage
 
@@ -80,7 +80,7 @@ Run a local browser verification before calling the artifact ready:
 High-fidelity HTML prototype
 
 ### 输入资产
-- <PRD / product overview / interaction spec / state matrix / prototype review>
+- <Spec / product overview / interaction spec / state matrix / prototype review>
 
 ### 高保真产物
 - `docs/design/prototypes/<feature>/index.html`
@@ -94,9 +94,9 @@ High-fidelity HTML prototype
 ### 验证证据
 - <render command or file open path, viewport checks, interaction checks>
 
-### 是否可进入 PRD 校准 / API 影响分析
+### 是否可进入 Spec 校准 / API 影响分析
 - <yes/no; list blocking gaps>
 
 ### 下一步
-- <PRD calibration / return to high-fidelity prototype / return to product-design-prototype>
+- <Spec calibration / return to high-fidelity prototype / return to product-design-prototype>
 ```

package/template/.agents/skills/high-fidelity-html-prototype/agents/openai.yaml

@@ -0,0 +1,5 @@
+version: 1
+interface:
+  display_name: "High Fidelity HTML Prototype"
+  short_description: "Ant Design v6 interactive HTML prototype gate"
+  default_prompt: "Use $high-fidelity-html-prototype to create an Ant Design v6 high-fidelity interactive HTML prototype after low-fidelity prototype review."

package/template/.agents/skills/implement/SKILL.md

@@ -1,10 +1,10 @@
 ---
 name: implement
-description: "Implement a piece of work based on a PRD or set of issues."
+description: "Implement a piece of work based on a spec or set of tickets."
 disable-model-invocation: true
 ---
 
-Implement the work described by the user in the PRD or issues.
+Implement the work described by the user in the spec or tickets.
 
 Use /tdd where possible, at pre-agreed seams.
 

package/template/.agents/skills/implement/agents/openai.yaml

@@ -0,0 +1,5 @@
+interface:
+  display_name: "Implement"
+  short_description: "Build work from a spec or tickets"
+policy:
+  allow_implicit_invocation: false

package/template/.agents/skills/improve-codebase-architecture/SKILL.md

@@ -17,6 +17,11 @@ This command is _informed_ by the project's domain model and built on a shared d
 
 ### 1. Explore
 
+**Scope before you scan — YAGNI.** Deepening a module pays off by making future changes to it easier, so put extra weight on the parts of the codebase that have recently changed. Decide *where* to look before you look:
+
+- If the user named a direction — a module, a subsystem, a pain point — take it, and skip the inference below.
+- Otherwise, walk back a good stretch of the commit history (`git log --oneline`) to find the codebase's hot spots — the files and areas that keep coming up — and let those paths pull your attention first. If the changes are scattered with no clear hot spot, widen the net.
+
 Read the project's domain glossary (`CONTEXT.md`) and any ADRs in the area you're touching first.
 
 Then use the Agent tool with `subagent_type=Explore` to walk the codebase. Don't follow rigid heuristics — explore organically and note where you experience friction:
@@ -56,7 +61,7 @@ Do NOT propose interfaces yet. After the file is written, ask the user: "Which o
 
 ### 3. Grilling loop
 
-Once the user picks a candidate, run the `/grilling` skill to walk the design tree with them — constraints, dependencies, the shape of the deepened module, what sits behind the seam, what tests survive.
+Once the user picks a candidate, run the `/grilling` skill to walk the decision tree with them — constraints, dependencies, the shape of the deepened module, what sits behind the seam, what tests survive.
 
 Side effects happen inline as decisions crystallize — run the `/domain-modeling` skill to keep the domain model current as you go:
 

package/template/.agents/skills/improve-codebase-architecture/agents/openai.yaml

@@ -0,0 +1,5 @@
+interface:
+  display_name: "Improve Codebase Architecture"
+  short_description: "Find and grill architecture improvements"
+policy:
+  allow_implicit_invocation: false

package/template/.agents/skills/lombok/SKILL.md

@@ -0,0 +1,345 @@
+---
+name: lombok
+description: |
+  Project Lombok for reducing Java boilerplate. Covers annotations for getters,
+  setters, constructors, builders, logging, and more. Based on production
+  patterns from castellino and gestionale-presenze projects.
+
+  USE WHEN: user mentions "lombok", "@Data", "@Builder", "@Slf4j", asks about
+  "boilerplate reduction", "getters/setters", "@RequiredArgsConstructor", "@Value"
+
+  DO NOT USE FOR: Java language features - use `java` skill instead
+  DO NOT USE FOR: MapStruct integration - use `mapstruct` skill
+  DO NOT USE FOR: Spring annotations - use `backend-spring-boot` skill
+allowed-tools: Read, Grep, Glob, Write, Edit
+---
+# Project Lombok
+
+> **Deep Knowledge**: Use `mcp__documentation__fetch_docs` with technology: `lombok` for comprehensive documentation.
+
+## Maven Configuration
+
+```xml
+<dependency>
+    <groupId>org.projectlombok</groupId>
+    <artifactId>lombok</artifactId>
+    <version>1.18.34</version>
+    <optional>true</optional>
+</dependency>
+
+<!-- For MapStruct compatibility -->
+<dependency>
+    <groupId>org.projectlombok</groupId>
+    <artifactId>lombok-mapstruct-binding</artifactId>
+    <version>0.2.0</version>
+</dependency>
+```
+
+## Common Annotations
+
+### @Data (All-in-One)
+
+```java
+@Data
+public class User {
+    private Long id;
+    private String name;
+    private String email;
+}
+
+// Generates:
+// - @Getter for all fields
+// - @Setter for all non-final fields
+// - @ToString
+// - @EqualsAndHashCode
+// - @RequiredArgsConstructor
+```
+
+### @Getter / @Setter
+
+```java
+public class User {
+    @Getter @Setter
+    private String name;
+
+    @Getter // Read-only
+    private final String email;
+
+    @Setter(AccessLevel.PROTECTED)
+    private String internalId;
+}
+```
+
+### @NoArgsConstructor / @AllArgsConstructor / @RequiredArgsConstructor
+
+```java
+@NoArgsConstructor
+@AllArgsConstructor
+public class User {
+    private Long id;
+    private String name;
+}
+
+@RequiredArgsConstructor
+public class UserService {
+    private final UserRepository userRepository; // Included in constructor
+    private final UserMapper userMapper;         // Included in constructor
+    private String cacheName;                    // NOT included
+}
+```
+
+### @Builder
+
+```java
+@Data
+@Builder
+public class User {
+    private Long id;
+    private String name;
+    private String email;
+    @Builder.Default
+    private UserStatus status = UserStatus.ACTIVE;
+}
+
+// Usage
+User user = User.builder()
+    .name("John")
+    .email("john@example.com")
+    .build();
+
+// With toBuilder for updates
+User updated = user.toBuilder()
+    .name("Jane")
+    .build();
+```
+
+### @Value (Immutable)
+
+```java
+@Value
+public class UserResponse {
+    Long id;
+    String name;
+    String email;
+    LocalDateTime createdAt;
+}
+
+// Generates:
+// - All fields are private final
+// - @AllArgsConstructor
+// - @Getter (no setters)
+// - @ToString
+// - @EqualsAndHashCode
+```
+
+## Entity Pattern
+
+```java
+@Entity
+@Table(name = "users")
+@Data
+@NoArgsConstructor
+@AllArgsConstructor
+@Builder
+@EntityListeners(AuditingEntityListener.class)
+public class User {
+
+    @Id
+    @GeneratedValue(strategy = GenerationType.IDENTITY)
+    private Long id;
+
+    @Column(nullable = false)
+    private String name;
+
+    @Column(unique = true, nullable = false)
+    private String email;
+
+    @Enumerated(EnumType.STRING)
+    @Builder.Default
+    private UserStatus status = UserStatus.ACTIVE;
+
+    @CreatedDate
+    @Column(updatable = false)
+    private LocalDateTime createdAt;
+
+    @LastModifiedDate
+    private LocalDateTime updatedAt;
+
+    // Exclude from toString/equals for performance
+    @ToString.Exclude
+    @EqualsAndHashCode.Exclude
+    @ManyToOne(fetch = FetchType.LAZY)
+    @JoinColumn(name = "department_id")
+    private Department department;
+}
+```
+
+## Service Pattern with Constructor Injection
+
+```java
+@Service
+@RequiredArgsConstructor
+@Slf4j
+public class UserServiceImpl implements UserService {
+
+    private final UserRepository userRepository;
+    private final UserMapper userMapper;
+    private final PasswordEncoder passwordEncoder;
+
+    @Override
+    public UserResponse create(CreateUserRequest dto) {
+        log.info("Creating user: {}", dto.getEmail());
+        User user = userMapper.toEntity(dto);
+        return userMapper.toResponse(userRepository.save(user));
+    }
+}
+```
+
+## Logging
+
+```java
+@Slf4j  // SLF4J logger
+public class UserService {
+    public void process() {
+        log.info("Processing...");
+        log.debug("Debug info: {}", data);
+        log.error("Error occurred", exception);
+    }
+}
+
+@Log4j2  // Log4j2 logger
+@CommonsLog  // Apache Commons Logging
+@JBossLog  // JBoss Logging
+```
+
+## DTO Pattern
+
+```java
+// Request DTO
+@Data
+public class CreateUserRequest {
+    @NotBlank
+    private String name;
+    @Email
+    private String email;
+    @Size(min = 8)
+    private String password;
+}
+
+// Response DTO (immutable)
+@Value
+@Builder
+public class UserResponse {
+    Long id;
+    String name;
+    String email;
+    UserStatus status;
+    LocalDateTime createdAt;
+}
+```
+
+## @Cleanup
+
+```java
+public void readFile(String path) throws IOException {
+    @Cleanup InputStream in = new FileInputStream(path);
+    // in.close() called automatically
+}
+```
+
+## @SneakyThrows
+
+```java
+@SneakyThrows  // Wraps checked exception
+public String readConfig() {
+    return Files.readString(Path.of("config.json"));
+}
+```
+
+## @Synchronized
+
+```java
+public class Counter {
+    @Synchronized
+    public void increment() {
+        // Thread-safe
+    }
+}
+```
+
+## @With (Immutable Updates)
+
+```java
+@Value
+@With
+public class Point {
+    int x;
+    int y;
+}
+
+Point p1 = new Point(1, 2);
+Point p2 = p1.withX(5);  // Point(5, 2)
+```
+
+## Key Annotations
+
+| Annotation | Purpose |
+|------------|---------|
+| `@Data` | Getter, Setter, ToString, Equals, Constructor |
+| `@Value` | Immutable class |
+| `@Builder` | Builder pattern |
+| `@RequiredArgsConstructor` | Constructor for final fields |
+| `@Slf4j` | Logger field |
+| `@ToString.Exclude` | Exclude from toString |
+| `@EqualsAndHashCode.Exclude` | Exclude from equals/hashCode |
+
+---
+
+## When NOT to Use This Skill
+
+| Scenario | Use Instead |
+|----------|-------------|
+| Java core language | `java` skill |
+| MapStruct mapping | `mapstruct` skill |
+| Spring annotations | `backend-spring-boot` skill |
+| JPA entities complex logic | Manual implementation |
+| Public API design | Explicit methods for clarity |
+
+---
+
+## Anti-Patterns
+
+| Anti-Pattern | Why It's Bad | Correct Approach |
+|--------------|--------------|------------------|
+| @Data on JPA entities | toString/equals issues | Use @Getter/@Setter selectively |
+| Not excluding lazy relations | LazyInitializationException | Use @ToString.Exclude |
+| @EqualsAndHashCode on entities | Proxy issues | Use @EqualsAndHashCode(onlyExplicitlyIncluded = true) |
+| @SneakyThrows everywhere | Hides exceptions | Use proper exception handling |
+| @Builder without @Default | Null fields | Add @Builder.Default |
+| @Value with mutable fields | Breaks immutability | Use only immutable types |
+| Mixing @Data and manual methods | Confusing API | Be consistent |
+| Not configuring in lombok.config | Inconsistent behavior | Use lombok.config file |
+
+---
+
+## Quick Troubleshooting
+
+| Issue | Cause | Solution |
+|-------|-------|----------|
+| "Cannot find symbol" for getters | IDE not processing | Enable annotation processing |
+| LazyInitializationException | toString on lazy relation | Add @ToString.Exclude |
+| MapStruct not working | Wrong processor order | Lombok before MapStruct |
+| Builder missing fields | No @Builder.Default | Add defaults or check config |
+| StackOverflowError in equals | Circular reference | Exclude relation fields |
+| IDE shows errors but compiles | IDE cache | Invalidate caches/restart |
+| @Slf4j logger not found | SLF4J not in classpath | Add SLF4J dependency |
+| Generated code not visible | delombok needed | Run delombok task |
+
+---
+
+## Reference Documentation
+- [Lombok Documentation](https://projectlombok.org/features/)
+- [Stable Features](https://projectlombok.org/features/all)
+- [Configuration](https://projectlombok.org/features/configuration)
+
+> **Deep Knowledge**: Use `mcp__documentation__fetch_docs` with technology: `lombok` for comprehensive documentation.