Skip to content

Non-techy usage pain points #633

Description

@lee-chase

Reported by a colleague, non-technical, who'd managed to follow all of our guidance to get started.

This included use of degit, installing of extension and running the project locally.

  1. Developer prefers typescript, pointed them at Support TypeScript #281
  2. They would have liked some basic guidance on taking a single design to code. Perhaps we can include a links to resources/guides in the README.
  3. Linter complaints when committing code, which fell into two categories
  • Formatting issues: Quick guidance on format on save or how to format manually.
  • Spelling issues: While thejr agentic AI wrote code it often used technical terms and abbreviations that were not in the dictionary.

The linter issues can largely be worked around by asking to complete the task, but this burns more tokens.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions