Compare commits

...

4 Commits

Author SHA1 Message Date
siujamo 2625fac6d8 feat: register british-english, commit-message, and spring-boot skills 2026-06-22 11:46:08 +08:00
siujamo a7fa29e3ec feat: add skills.json marketplace manifest 2026-06-22 11:23:09 +08:00
siujamo e10bcfa734 @
docs(british-english): remove redundant guidance line

The "Follow these rules consistently throughout a document." line
added no real directive beyond what the rule sections already convey,
and the "a document" framing was too narrow for outputs like commit
messages and code comments.
@
2026-06-16 17:21:31 +08:00
siujamo 3be04dab3a docs(spring-boot): align examples with documented conventions
Two consistency cleanups:

- Drop redundant column aliases in the MyBatis Mapper example; map-underscore-to-camel-case is already enabled in application.yml, so the explicit aliases are noise.
- Re-nest the request/response directories under a top-level domain/ package in the end-to-end example to match the project layout shown earlier in the skill. The transfer-objects section already refers to com.example.app.domain.request.* and com.example.app.domain.response.* implicitly via the layout tree.

Also drops the now-orphaned 阿里巴巴《Java 开发手册》 line from Authoritative References, since the rest of the skill no longer leans on it for terminology.
2026-06-16 15:36:12 +08:00
3 changed files with 36 additions and 10 deletions
+1 -1
View File
@@ -5,7 +5,7 @@ description: Apply British English spelling and grammar as a global default when
# British English
Conventions for writing in British English, as distinct from American English. Follow these rules consistently throughout a document.
Conventions for writing in British English, as distinct from American English.
## Spelling
+26
View File
@@ -0,0 +1,26 @@
{
"name": "Claude Code Skills",
"skills": [
{
"name": "british-english",
"description": "Apply British English spelling and grammar conventions to project documents and code",
"repository": "https://onixbyte.dev/onixbyte/claude-code-skills",
"branch": "main",
"path": "british-english"
},
{
"name": "commit-message",
"description": "Generate well-formatted git commit messages following conventional commits",
"repository": "https://onixbyte.dev/onixbyte/claude-code-skills",
"branch": "main",
"path": "commit-message"
},
{
"name": "spring-boot",
"description": "Add JPA CRUD resources following Spring Boot layered architecture",
"repository": "https://onixbyte.dev/onixbyte/claude-code-skills",
"branch": "main",
"path": "spring-boot"
}
]
}
+9 -9
View File
@@ -507,14 +507,14 @@ A protected no-arg constructor is required by JPA. Static factories (`fromReques
public interface UserMapper {
@Select("""
SELECT id, email, display_name AS displayName, status, created_at AS createdAt
SELECT id, email, display_name, status, created_at
FROM users
WHERE id = #{id}
""")
Optional<UserEntity> findById(Long id);
@Select("""
SELECT id, email, display_name AS displayName, status, created_at AS createdAt
SELECT id, email, display_name, status, created_at
FROM users
<where>
<if test="email != null">AND email LIKE CONCAT('%', #{email}, '%')</if>
@@ -780,12 +780,13 @@ com.example.app/
│ └── UserMapper.java (MyBatis, when needed)
├── entity/
│ └── UserEntity.java
├── request/
│ ├── CreateUserRequest.java
│ ├── UpdateUserRequest.java
└── UserSearchCriteria.java
├── response/
│ └── UserResponse.java
├── domain/
│ ├── request/
│ ├── CreateUserRequest.java
│ ├── UpdateUserRequest.java
│ │ └── UserSearchCriteria.java
│ └── response/
│ └── UserResponse.java
└── enums/
└── UserStatus.java
```
@@ -822,4 +823,3 @@ public class App {
- Spring Data JPA Reference
- Jakarta Bean Validation 3.0
- springdoc-openapi 2.x
- 阿里巴巴《Java 开发手册》(层结构、Manager/Client 命名来源)