1. **Diagnose First:** Read the relevant code carefully. Identify the root cause
not just symptoms.
Explore
12,156 skills indexed with the new KISS metadata standard.
not just symptoms.
public API surface
naming conventions
not the other way around.** Every structural decision must justify itself through improved developer velocity
debug complex structural issues
refactor existing C# code for better architecture
system design
concise
concise
`# ROLE:
few-shot
legal
e.g. “You are a senior front-end engineer…”.
legal analyst
robust prompt.
calling APIs) instead of prompt design.
viết bài
if you find any fix it.
such as personalization and real-time synthesis
tailored to different user skill levels
{
and nothing else. Do not write explanations. Do not type commands unless I instruct you to do so. when i need to tell you something in english
use Swift unless the user specifies otherwise.
with code snippets or commands where applicable]