vibetags: Skill for Claude Code

VibeTags Usage Guide

VibeTags is a compile-time Java annotation processor that generates AI platform-specific guardrail files from source annotations. Zero runtime overhead — all annotations have RetentionPolicy.SOURCE.

Quick Setup

1. Add the two artifacts

VibeTags ships as two artifacts and you need both. Depending on only one of them is the most common "VibeTags is broken" report, and neither failure produces a useful error:

Maven. Annotations as an ordinary dependency, processor on annotationProcessorPaths:

<dependencies>
    <dependency>
        <groupId>se.deversity.vibetags</groupId>
        <artifactId>vibetags-annotations</artifactId>
        <version>1.3.2</version>
    </dependency>
</dependencies>

<build>
    <plugins>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-compiler-plugin</artifactId>
            <configuration>
                <annotationProcessorPaths>
                    <path>
                        <groupId>se.deversity.vibetags</groupId>
                        <artifactId>vibetags-processor</artifactId>
                        <version>1.3.2</version>
                    </path>
                </annotationProcessorPaths>
            </configuration>
        </plugin>
    </plugins>
</build>

Do not declare vibetags-processor as a plain <scope>provided</scope> dependency instead of the block above. Since JDK 23, javac no longer discovers processors sitting on the class path, so that shape compiles cleanly and writes no files: no error, no warning. If the processor has to stay on the class path, add <proc>full</proc> to the compiler plugin's configuration.