Rewrite a project's README.md so it doubles as an interview walkthrough guide the author can read and confidently explain the project from. Use when the user asks to "make the README interview-ready", "rewrite the README as an interview guide", "help me explain this project in an interview", "write a README I can walk an interviewer through", "prepare this project for interviews", or invokes /interview-readme. Also trigger when the user has an interview coming up and wants to answer "Can you walk me through this project?" for a repo they built. The rewritten README explains, in simple English, what the project does, the problem it solves, the overall architecture, the technologies used and why they were chosen, how the main features work, the request/response flow, key technical decisions and trade-offs, challenges faced and how they were solved, and possible future improvements. Not for adding badges, topic tags, or GitHub discoverability work — use github-repo-seo for that.
Production-grade Spring Boot for Java services that own money and state. This skill MUST be loaded when ANY .java file, pom.xml, build.gradle, build.gradle.kts, application.yml, application.yaml, application.properties, or Flyway migration (V*__*.sql, R__*.sql) belonging to a Spring project is being read, reviewed, edited, or created. Also use when the user asks to "create a Spring Boot app", "scaffold a Spring service", "add a REST controller", "add an endpoint", "create a repository", "write a DAO", "use JdbcClient", "use JdbcTemplate", "write raw SQL in Spring", "add @Transactional", "fix a transaction that isn't rolling back", "make this endpoint idempotent", "handle the Idempotency-Key header", "implement the transactional outbox", "publish events reliably", "fix a race condition", "prevent duplicate charges", "prevent double-posting", "add a Flyway migration", "add liveness and readiness probes", "add Actuator", "graceful shutdown", "containerize a Spring Boot app", "write a Dockerfile for a jar", "writ