Skip to main content

Documentation-First Approach

The recommended way to use PullUp is with documentation files. PullUp automatically extracts URLs, credentials, pages, and features.

Single Documentation File

Create app-info.md:
Generate skill:

Documentation Folder

PullUp automatically extracts:
  • URLs (http://… or localhost:…)
  • Page paths (starting with /)
  • Credentials (email/password patterns)
  • Features (headings, bullet points)

Guided Exploration

Use the --prompt flag to provide context:

Example: E-commerce Site

Example: SaaS Dashboard

Example: Simple Landing Page

Control Exploration

Depth and Page Limits

Verbose Output

Updating Skills

When your application changes:

Custom Output Location

Using Generated Skills

After creation, use the skill naturally:

Best Practices

Enable exploration of authenticated areas by providing test credentials in your documentation files.
List important pages in your documentation to ensure they’re discovered and mapped.
Provide application-specific context to help PullUp prioritize and understand your app better.
Begin with --max-pages 25 and increase as needed. Faster iteration during initial setup.
Re-run PullUp when you add significant features to keep the skill current.
Check ~/.claude/skills/yourapp-testing/app-knowledge.json to verify accuracy.

Generated Skill Structure

When PullUp completes, you’ll get:

What’s Included

  • Pages discovered - All URLs, titles, and page types
  • Forms mapped - Input fields, buttons, validation
  • User flows - Login, signup, checkout sequences
  • Test data - Appropriate values for each form field
  • Navigation - Site structure and hierarchy

Team Collaboration

Share generated skills with your team:
Skills are portable and self-contained. Team members don’t need to re-run PullUp.

Next Steps

View on GitHub

Star the repository and see more examples

Report Issues

Found a bug or have a feature request?