Skip to content
Kisuke Kisuke

Getting Started

This guide walks you through your first interaction with Claude in Kisuke.

Prerequisites

Section titled “Prerequisites”

Before starting:

  • Kisuke app installed and configured
  • Active connection to a space
  • Basic familiarity with the Kisuke interface

Opening Claude Chat

Section titled “Opening Claude Chat”
  1. Launch Kisuke and connect to your space
  2. Tap the Chat tab in the bottom navigation
  3. The chat interface opens with an empty conversation

Your first request

Section titled “Your first request”

Basic code question

Section titled “Basic code question”

Start with a straightforward programming question:

How do I read a JSON file in Python?

Claude will respond with:

  • Explanation of the approach
  • Code example
  • Common error handling

Working with your files

Section titled “Working with your files”

Request help with existing code:

Can you explain what the function in utils.js does?

Claude will:

  1. Read the specified file
  2. Analyze the function
  3. Provide a clear explanation

Making code changes

Section titled “Making code changes”

Ask Claude to modify your code:

Add error handling to the fetchData function in api.js

Claude will:

  1. Read the current implementation
  2. Show the proposed changes
  3. Apply the modifications with your approval

Understanding Claude’s responses

Section titled “Understanding Claude’s responses”

Tool usage indicators

Section titled “Tool usage indicators”

When Claude uses tools, you’ll see cards indicating:

  • Tool name - What action is being performed
  • Parameters - Details about the operation
  • Status - Progress and completion state
  • Results - Output or changes made

Code formatting

Section titled “Code formatting”

Claude formats code responses with:

  • Syntax highlighting
  • Language indicators
  • Copy button for easy reuse

Explanations

Section titled “Explanations”

Claude provides context for code changes:

  • Why specific approaches are recommended
  • Potential edge cases to consider
  • Performance implications

Common first tasks

Section titled “Common first tasks”

Debug an error

Section titled “Debug an error”

Share an error message and relevant code:

I'm getting "TypeError: cannot read property 'length' of undefined"
in this function: [paste code]

Create a new feature

Section titled “Create a new feature”

Describe what you need:

Create a React component that displays a user profile card with
name, email, and avatar image

Understand existing code

Section titled “Understand existing code”

Point to specific files:

What does the authentication flow in auth.js do?

Refactor code

Section titled “Refactor code”

Request improvements:

Can you refactor this function to use async/await instead of callbacks?

Working with responses

Section titled “Working with responses”

Reviewing changes

Section titled “Reviewing changes”

Before accepting file modifications:

  1. Read the proposed changes
  2. Understand the reasoning
  3. Check for unintended effects
  4. Approve or request adjustments

Asking follow-up questions

Section titled “Asking follow-up questions”

Build on previous responses:

  • “Can you add input validation to that function?”
  • “What about error handling for network failures?”
  • “How would I test this code?”

Providing feedback

Section titled “Providing feedback”

If the response isn’t quite right:

  • Clarify your requirements
  • Point out specific issues
  • Request alternative approaches

Managing your session

Section titled “Managing your session”

Starting fresh

Section titled “Starting fresh”

Create a new tab when:

  • Switching to a different topic
  • Beginning a new feature
  • The conversation becomes too long

Referencing context

Section titled “Referencing context”

Claude remembers the conversation:

  • Previous code discussed
  • Files already examined
  • Decisions made earlier

Cost awareness

Section titled “Cost awareness”

Monitor token usage displayed in the interface:

  • Each message shows token count
  • Running total visible in status bar
  • Costs update in real-time

Tips for effective use

Section titled “Tips for effective use”

Be specific

Section titled “Be specific”

More detail yields better results:

Instead of:

Fix the bug

Try:

The login function fails when the email field is empty.
Please add validation to check for required fields.

Provide context

Section titled “Provide context”

Include relevant information:

  • Programming language and version
  • Framework or libraries used
  • Expected vs. actual behavior
  • Error messages in full

Work incrementally

Section titled “Work incrementally”

Break complex tasks into steps:

  1. Implement basic functionality
  2. Add error handling
  3. Include edge cases
  4. Optimize performance

Next steps

Section titled “Next steps”