vilt-coding-standards
Apply VILT stack coding standards when writing Vue, Laravel, or TypeScript code. Automatically enforces patterns for Composition API, Form Requests, Inertia navigation, and component hierarchy. Activates when creating or modifying Vue components, Laravel controllers, services, or models.
What this skill does
# VILT Coding Standards
Apply these standards when writing code in ResRequest projects.
## Vue Components
### Script Setup Syntax
Always use `<script setup lang="ts">`:
```vue
<script setup lang="ts">
import { ref, computed } from 'vue'
import { useForm } from '@inertiajs/vue3'
import { Button } from '@/components/ui/button'
interface Props {
items: Item[]
}
const props = defineProps<Props>()
</script>
```
### TypeScript Interfaces
Define interfaces for all props and emits:
```typescript
interface Props {
user: User
isEditing?: boolean
}
interface Emits {
(e: 'saved', user: User): void
(e: 'cancelled'): void
}
const props = defineProps<Props>()
const emit = defineEmits<Emits>()
```
### Composition API Only
Never use Options API. Always use Composition API:
```typescript
// CORRECT: Composition API
const count = ref(0)
const doubleCount = computed(() => count.value * 2)
function increment() {
count.value++
}
// WRONG: Options API
export default {
data() {
return { count: 0 }
},
computed: {
doubleCount() { return this.count * 2 }
}
}
```
### Form Handling
Always use `useForm()` from Inertia for forms:
```typescript
import { useForm } from '@inertiajs/vue3'
const form = useForm({
name: '',
email: '',
})
function submit() {
form.post(route('users.store'), {
preserveScroll: true,
onSuccess: () => form.reset(),
})
}
```
## Laravel Controllers
### Form Request Validation
Always use Form Request classes:
```php
// CORRECT: Form Request
public function store(CreateUserRequest $request): RedirectResponse
{
User::create($request->validated());
return redirect()->back();
}
// WRONG: Inline validation
public function store(Request $request): RedirectResponse
{
$validated = $request->validate([...]);
}
```
### Resource Transformation
Use Resources for API/Inertia responses:
```php
public function index(): Response
{
return Inertia::render('Users/Index', [
'users' => UserResource::collection(User::all()),
]);
}
```
### Happy Path Last
Handle errors first, success case last:
```php
public function store(CreateUserRequest $request): RedirectResponse
{
if (! $request->user()->canCreateUsers()) {
abort(403);
}
if (User::where('email', $request->email)->exists()) {
return redirect()->back()->withErrors(['email' => 'Email already exists']);
}
// Happy path last
User::create($request->validated());
return redirect()->route('users.index');
}
```
### Authorization First
Always authorize before action:
```php
public function destroy(User $user): RedirectResponse
{
$this->authorize('delete', $user);
$user->delete();
return redirect()->route('users.index');
}
```
## Laravel Services
### Typed Properties
Use typed properties, not docblocks:
```php
class UserService
{
public function __construct(
private UserRepository $repository,
private EmailService $emailService,
) {}
}
```
### Return Types
Always specify return types including void:
```php
public function createUser(array $data): User
{
return User::create($data);
}
public function sendNotification(User $user): void
{
// ...
}
```
## Laravel Models
### Typed Casts
Use typed casts array:
```php
protected $casts = [
'is_active' => 'boolean',
'metadata' => 'array',
'published_at' => 'datetime',
];
```
### Relationship Return Types
Type hint relationships:
```php
public function posts(): HasMany
{
return $this->hasMany(Post::class);
}
public function profile(): HasOne
{
return $this->hasOne(Profile::class);
}
```
## TypeScript Conventions
### No any Type
Never use `any`. Use proper types or `unknown`:
```typescript
// WRONG
function process(data: any) { }
// CORRECT
function process(data: unknown) { }
function process(data: Record<string, string>) { }
```
### Interface Over Type
Prefer interfaces for object shapes:
```typescript
// CORRECT
interface User {
id: number
name: string
}
// Less preferred (but OK for unions/intersections)
type UserId = number | string
```
## Code Quality
### No Debugging Code
Never commit:
- `console.log()`, `console.debug()`
- `dd()`, `dump()`, `ray()`
- `debugger` statements
### No Unnecessary Comments
Write self-documenting code. Only comment WHY, not WHAT:
```php
// WRONG: Comment explains what code does
// Get the user
$user = User::find($id);
// CORRECT: Comment explains why
// Using findOrFail would throw before we can show custom error
$user = User::find($id);
if (! $user) {
return $this->userNotFoundResponse($id);
}
```
### Translations
All user-facing strings must use translations:
```vue
<!-- Vue -->
<Button>{{ $t('common.save') }}</Button>
```
```php
// Laravel
return redirect()->back()->with('success', __('users.created'));
```
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.