Claude Code - herougo/SoftwareEngineerKnowledgeRepository GitHub Wiki

Unresolved Questions

  1. What's the best way to input line numbers (e.g. "This function should be used for X")?
  2. Does /plan just enter plan mode? Is that all it does?

Installation

https://code.claude.com/docs/en/overview#terminal

Starting Claude Code (Windows)

Run claude in cmd

Commands Within Claude

Source

Command Description
/init "Initialize project with CLAUDE.md guide"
/clear "clears the conversation history" (of the chat I assume?)
/context "Visualize current context usage as a colored grid"
/help "Get usage help"
/permissions "View or update permissions"
/model "Select or change the AI model" (use the left/right arrows to adjust effort level)
/resume Resume a conversation (opens the session picker)
/mcp "Manage MCP server connections and OAuth authentication"
/plan "Enter plan mode directly from the prompt"

Example Permissions

{
  "permissions": {
    "allow": [
      "Bash(npm run test *)",
      "Bash(git commit *)",
    ],
    "deny": [
      "Bash(git push *)"
    ]
  }
}

Claude Code Hooks (TODO: Explore Further)

"Claude Code hooks provide a way to register custom shell commands to perform permission evaluation at runtime. When Claude Code makes a tool call, PreToolUse hooks run before the permission system, and the hook output can determine whether to approve or deny the tool call in place of the permission system."

Claude.md

"A markdown file where you store project-specific instructions, conventions, and context that Claude should know every session."

Note

  • there is a global Claude.md file and a project-specific Claude.md file

Tips

  • Joe Kim (youtuber) recommends aim for about 300 lines.
  • Minimize its size to keep the context clean.
  • Some recommend against using knowledge from /init (this would be stuff Claude can figure out on its own anyways)
  • Include a critical rules section for "always do this" or "never do this" (e.g. past Claude mistakes)

Skills

https://code.claude.com/docs/en/skills

"Skills extend what Claude can do. Create a SKILL.md file with instructions, and Claude adds it to its toolkit. Claude uses skills when relevant, or you can invoke one directly with /skill-name."

Where skills live

Location Path Applies to
Personal ~/.claude/skills/<skill-name>/SKILL.md All your projects
Project .claude/skills/<skill-name>/SKILL.md This project only

Folder structure

my-skill/
├── SKILL.md           # Main instructions (required)
├── template.md        # Template for Claude to fill in
├── examples/
│   └── sample.md      # Example output showing expected format
└── scripts/
    └── validate.sh    # Script Claude can execute

The SKILL.md contains the main instructions and is required.

Main Workflow

(TODO)

MCP

Note: MCP can blow up the context window.

Keyboard Shortcuts

  • double escape: clears textbox keyboard shortcut

Prompt Snippets

  1. Put what we just did in a skill

Other Tips

February 23, 2026: Consider using Opus 4.5 over Sonnet 4.5

FAQ

  1. How do I input images?

    • You can drag images to the terminal "textbox".

  2. What if I want to assign custom aliases to key prompts (e.g. alias make-skill='Put what we just did in a skill')? Is there a way to make custom commands?

    • Yes. Look into skills!

  3. How do I see code changes?

    • Reddit says to use git.

  4. Should I commit skills to the repo itself?

    • Google says absolutely!
⚠️ **GitHub.com Fallback** ⚠️