# June Style

> Provides June's design, coding-discipline, and formatting guidance. Use for design work or code changes that need this style.

- Skill: `lemonorangeapple/june-style` (Agent Skill)
- Install (CLI): `npx skillmds@latest add lemonorangeapple/june-style`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lemonorangeapple/june-style/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: lemonorangeapple (https://skillmd.com/u/lemonorangeapple)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lemonorangeapple/june-style

---


# June Style

## Design Guide

- Never use outdated style like blue-purple gradient style. Prefer light blue outline style unless the user wants another style.

### Banners

Design banners for platform sizes. Keep content inside the safe zone, use one CTA, and keep type short.

### Logo

Use logo work when the user needs a brand mark. Prefer a white background and an explicit style.

### Design System

Use three-layer tokens. Keep primitive, semantic, and component layers separate. Do not hardcode raw hex values when tokens exist.

### Slides

Use slides for persuasive HTML presentations. Use tokens, CSS variables, Chart.js, and simple navigation.

### Icons

Use icons when the user wants clean SVG assets. Pick the style first and keep shapes readable.

### Social Photos

Use the social-photo workflow for platform-specific images. Export at the exact size.

## Code Guide

### Base Guide

Use Karpathy-style discipline whenever writing or changing code.

1. State assumptions before acting if anything is unclear.
2. Pick the simplest solution that solves the request.
3. Touch only what the request needs.
4. Define success in a way that can be checked.

### Code Style

#### Note Use

1. Never use unnecessary notes for code.
2. It is necessary to make up to five lines of notes for each file in its header.
3. It is recommended to use only one line of notes for a function in its definition.

#### Indent and Braces Style

Never use tabs; use 4 spaces instead.

Use indentation and braces like this:

```cpp
void func() {
    return;
}
```

#### New Feature Use

Always opt for modern language features when they provide performance improvements while maintaining the same functionality. For example, prefer `unordered_map` over `map` when applicable.