lemonorangeapple 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.
- State assumptions before acting if anything is unclear.
- Pick the simplest solution that solves the request.
- Touch only what the request needs.
- Define success in a way that can be checked.
Code Style
Note Use
- Never use unnecessary notes for code.
- It is necessary to make up to five lines of notes for each file in its header.
- 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:
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.