| Strategy | Description | Typical Implementation | Advantages | Risks/Trade-offs |
|---|---|---|---|---|
| Context Offloading | Moving parts of the working co |
| --- | |
| name: frontend-design | |
| description: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics. | |
| license: Complete terms in LICENSE.txt | |
| --- | |
| This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices. | |
| The user provides frontend requirements: a component, page, application, or interface to build. They may include context about the purpose, audience, or technical constraints. |
| name | description | version | author |
|---|---|---|---|
spreadsheet-generator |
Generate professional Excel spreadsheets with data, charts, and formatting using Claude and Anthropic's xlsx skill |
1.0.0 |
VTCode Team |
Generate professional Excel spreadsheets with structured data, formulas, charts, and professional formatting. This skill leverages Anthropic's xlsx Agent Skill to create Excel documents programmatically.
| # To permanently store config options, create a config.toml file located in your config directory: | |
| # Linux and Mac: ~/.config/helix/config.toml | |
| # Windows: %AppData%\helix\config.toml | |
| theme = "onedark" | |
| [editor] | |
| # Show currently open buffers, only when more than one exists. | |
| bufferline = "multiple" | |
| # Highlight all lines with a cursor |
Prompt structure
Task context
Tone context
Background data, documents, and images
Detailed task description & rules
Examples
Conversation history
Immediate task description or request
A list of commonly asked questions, design decisions, reasons why Clojure is the way it is as they were answered directly by Rich (even when from many years ago, those answers are pretty much valid today!). Feel free to point friends and colleagues here next time they ask (again). Answers are pasted verbatim (I've made small adjustments for readibility, but never changed a sentence) from mailing lists, articles, chats.
How to use:
- The link in the table of content jumps at the copy of the answer on this page.
- The link on the answer itself points back at the original post.
This is a compiled list of falsehoods programmers tend to believe about working with time.
Don't re-invent a date time library yourself. If you think you understand everything about time, you're probably doing it wrong.
- There are always 24 hours in a day.
- February is always 28 days long.
- Any 24-hour period will always begin and end in the same day (or week, or month).
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <meta name="viewport" content="width=device-width, initial-scale=1"> | |
| <title>Vinh Nguyen | iOS Engineer</title> | |
| <!-- SEO & sharing meta tags --> | |
| <meta name="description" |
| # train_grpo.py | |
| # | |
| # See https://github.com/willccbb/verifiers for ongoing developments | |
| # | |
| import re | |
| import torch | |
| from datasets import load_dataset, Dataset | |
| from transformers import AutoTokenizer, AutoModelForCausalLM | |
| from peft import LoraConfig | |
| from trl import GRPOConfig, GRPOTrainer |