1. **Analyze the Request:** * **Role:** News summarization expert. * **Task:** Summarize the provided article. * **Length:** Concisely in 2-4 sentences. * **Focus:** Most important information. * **Constraints:** Do not copy/paste, do not just restate the title (add new info), answer in English. * **Input:** Title ("Cursor Best Practices Skill by Hktitan"), Source ("hackernews"), Article Text (Just the title repeated). *Crucial Observation: The Article Text provided is extremely sparse or non-existent beyond the title.* 2. **Analyze the Input Text:** * "Cursor Best Practices Skill by Hktitan" * "Source: hackernews" * "Article Text: Cursor Best Practices Skill by Hktitan" 3. **Identify the Problem:** The user has provided a title and a source, but the *body* of the article is missing or essentially just repeats the title. There is no content to summarize other than the metadata. 4. **Formulate a Strategy:** * Since I cannot summarize content that doesn't exist, I need to infer what *usually* happens in such Hacker News threads or simply acknowledge the lack of content provided. * *Self-Correction:* Wait, looking at the prompt again, the user says "Summarize the following article". If the article text is empty/repetitive, I can't make up a summary of the content. However, usually in these types of prompts, if the text is just the title, the "article" might be a very short Hacker News "Show HN" post or the user made a mistake in copying the text. * *Hypothesis:* This looks like a "Show HN" post where "Hktitan" is
본문
cursor-best-practices cursor-best-practices A structured repository for creating and maintaining Cursor Best Practices optimized for agents and LLMs. This skill provides references/ (on-demand docs) and assets/templates/ (rule, command, and subagent templates) covering rules, commands, skills, subagents, ignore files, Agent security, workflows, and community resources. When to use Apply this skill when users: - Set up or initialize Cursor, create the .cursor folder, or ask "setup my .cursor folder" - Write or edit .cursor/rules , AGENTS.md, or rule frontmatter - Create or use slash commands, skills, or subagents - Configure .cursorignore or.cursorindexingignore - Work with Agent modes (Agent, Ask, Plan, Debug), semantic search, or @mentions - Ask about TDD, git-style commands, large codebases, or Cursor workflows - Discover rules or MCPs (cursor.directory) or skill recommendations (skills.sh) - Ask about plugins, hooks, Cloud Agent, CLI, worktrees, or deeplinks Rules Locations: Project .cursor/rules/ (.md /.mdc ), user Cursor Settings → Rules, Team dashboard. Precedence: Team → Project → User. Types and when to use: | Type | When to use | |---|---| | Always Apply | Must affect every request (e.g. "No any in TS", "Run tests before done"). Use sparingly. | | Apply Intelligently | General guidance when relevant (e.g. "Prefer functional components"). | | Apply to Specific Files | Use globs (e.g. **/*.test.ts , **/api/** ). Rule loads only when those files are in context. | | Apply Manually | User invokes with @rule-name when needed (e.g. release process, legacy quirks). | Frontmatter: description (keyword-rich, helps relevance), globs (file-specific), alwaysApply (use rarely). Keep each rule . Ignore files .cursorignore : Project root; same syntax as .gitignore . Excluded paths are not used for semantic search, Tab, Agent, Inline Edit, @mentions. Not terminal/MCP. Why: Security (secrets, keys, credentials), performance (large repos). .cursorindexingignore : Indexing only; files still usable if @-mentioned. Must exclude: .env , .env.* , *.key , *.pem , credentials.json , **/secrets/** . Add project-specific paths. Use ! carefully; parent exclusions limit re-includes. See: Ignore files. assets/templates/rules/ignore-cursorignore-secrets.md. Agent and security Agent: Rules + tools (search, read, edit, terminal, MCP) + your messages. Summarization (/summarize ), checkpoints. Queue (Enter) vs Ctrl+Enter (send immediately). Security: File edits allowed (except protected config); use VCS. Terminal: approval by default; avoid "Run everything". MCP: approve connection + each tool call. Network: GitHub, link fetch, search only. Put secrets in .cursorignore . See: Agent overview, Agent security. references/agent-and-security.md. Agent modes | Mode | Purpose | Tools | |---|---|---| | Agent | Implement, refactor, multi-file work. | Full (search, read, edit, terminal, MCP). | | Ask | Learning, Q&A, exploration. | Search + read only; no edits. | | Plan | Research → clarify → plan → you review → "Build". | Search + read. Plans in .cursor/plans/ ; Shift+Tab to switch. | | Debug | Reproducible bugs; hypotheses → instrument → reproduce → fix → verify. | Full. | Switch: Mode picker in chat; Ctrl+. to cycle. Best practice: Plan with Ask/Plan, implement with Agent. If Agent builds wrong thing, revert → refine plan → re-run. See: Plan Mode, Debug Mode. assets/templates/rules/modes-plan-then-agent.md. references/modes-context-tools.md. Workflows and large codebases TDD: Write tests → run (expect fail) → commit tests → implement → run until pass → commit impl. Run tests before done: assets/templates/rules/workflows-run-tests-before-done.md. Git-style commands: /pr , /fix-issue , /review , /update-deps , /docs in .cursor/commands/ . Codebase understanding: "How does X work?", "How do I add Y?"; broad → narrow. Diagrams: Ask for Mermaid architecture/data-flow. Hooks: .cursor/hooks.json for long-running loops. Design → code: Paste mockups; use Browser for preview. Large codebases: Domain rules in .cursor/rules with globs; Plan with Ask, implement with Agent. Tab = quick edits; Inline Edit (Ctrl+K) = single-file; Chat/Agent = multi-file. Use @files, @folder, @Code; scope down; new chats when context is noisy. See: Agent workflows, Large codebases. references/workflows-and-codebases.md. Semantic search, @mentions, Tab Semantic search: Meaning-based; natural-language questions. Indexing on workspace open; usable ~80% completion. Use both grep (exact) and semantic (conceptual): assets/templates/rules/context-use-grep-and-semantic.md. @Files & Folders: Reference by path; drag from sidebar. @Code: Specific snippets (most precise). @Docs: Bundled or Add new doc (URL). /summarize — compress context. Best practice: assets/templates/rules/context-use-at-mentions.md. Tab: Inline autocomplete; Tab accept, Esc reject, Ctrl+Right partial. Use for speed; Inline Edit or Chat for larger changes. See: Semantic search, @ Mentions, Tab. Bugbot, MCP, shortcut