Create Screen logo

Create Screen

Community
EmadBeltaje
create-screen

Creates a GetX screen module (controller, view, binding) under lib/app/modules and registers it in app routes. Use whenever the user asks to create a screen, page, or module, says get create screen, get create page, get create module, or wants a new GetX view plus controller plus binding with routing.

Overview

PublisherEmadBeltaje
Repositoryflutter_getx_template
Skill namecreate-screen
Stars
519
Forks
138
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by EmadBeltaje on GitHub. Read the source before you install it.

Installation

Install the Create Screen AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/EmadBeltaje/flutter_getx_template/tree/master/.agent/skills/create-screen
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/EmadBeltaje/flutter_getx_template.git /tmp/flutter_getx_template
mkdir -p .claude/skills
cp -r /tmp/flutter_getx_template/.agent/skills/create-screen .claude/skills/create-screen
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Create Screen in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Create Screen on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Create Screen is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Create screen

Scaffold a new GetX module: view, controller, binding, and route. This repo uses GetX Pattern (lib/app/modules). Write new screens there. Do not create lib/presentation — that layout is a different architecture and is not wired to AppPages.

Start from the templates in this skill, then add only extra UI or logic the user asked for. Existing modules may contain feature-specific API and widgets; those are not the scaffold.

Name

Take the screen name from the user (home, login, user profile, get create screen:home). Optional parent: on home / inside home / on the home module.

  1. Trim trailing screen, view, page, or module (any case) so LoginScreen becomes login.
  2. snake = snake_case. pascal = PascalCase.
  3. Classes are {pascal}View, {pascal}Controller, {pascal}Binding.
  4. Files are {snake}_view.dart, {snake}_controller.dart, {snake}_binding.dart.
  5. Route path segment is /{snake} with underscores turned into hyphens (user_profile → /user-profile).

Destination

Read pubspec.yaml for the package name.

Find a directory named modules under lib (this repo: lib/app/modules).

on parentFolder
none{modules}/{snake}/
givenFind a directory under lib whose path contains /{parent}/ as a segment (prefer {modules}/{parent}). Put the new module at {parent-dir}/{snake}/. If no such folder exists, stop and say so.

If that destination folder already exists, ask before overwriting. Do not silently replace it.

Create three subfolders: bindings/, controllers/, views/.

Files

Write all three from the templates below. Substitute {pascal}, {snake}, and keep relative imports.

controllers/{snake}_controller.dart

dart
import 'package:get/get.dart';

class {pascal}Controller extends GetxController {
  //TODO: Implement {pascal}Controller

  final count = 0.obs;

  @override
  void onInit() {
    super.onInit();
  }

  @override
  void onReady() {
    super.onReady();
  }

  @override
  void onClose() {
    super.onClose();
  }

  void increment() => count.value++;
}

views/{snake}_view.dart

dart
import 'package:flutter/material.dart';
import 'package:get/get.dart';

import '../controllers/{snake}_controller.dart';

class {pascal}View extends GetView<{pascal}Controller> {
  const {pascal}View({super.key});

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: const Text('{pascal}View'),
        centerTitle: true,
      ),
      body: const Center(
        child: Text(
          '{pascal}View is working',
          style: TextStyle(fontSize: 20),
        ),
      ),
    );
  }
}

bindings/{snake}_binding.dart

dart
import 'package:get/get.dart';

import '../controllers/{snake}_controller.dart';

class {pascal}Binding extends Bindings {
  @override
  void dependencies() {
    Get.lazyPut<{pascal}Controller>(
      () => {pascal}Controller(),
    );
  }
}

Routes

Find app_pages.dart and app_routes.dart under lib (this repo: lib/app/routes/). Match the identifier style already used in those files (this repo uses lowercase: home, not HOME).

app_routes.dart

Inside Routes, add:

dart
  static const {routeId} = _Paths.{routeId};

If this screen is nested (on a parent), instead:

dart
  static const {routeId} = _Paths.{parentId} + _Paths.{routeId};

Inside _Paths, add:

dart
  static const {routeId} = '/{route-segment}';

{routeId} matches existing style (login if the file uses home). {route-segment} is the snake name with _ → -.

app_pages.dart

Add relative imports next to the existing module imports:

dart
import '../modules/{path-from-modules}/bindings/{snake}_binding.dart';
import '../modules/{path-from-modules}/views/{snake}_view.dart';

{path-from-modules} is {snake} or {parent}/{snake}.

Insert a GetPage using the same shape already in the file:

dart
    GetPage(
      name: _Paths.{routeId},
      page: () => const {pascal}View(),
      binding: {pascal}Binding(),
    ),
  • Top-level: insert it in static final routes before the closing ];.
  • Nested (on parent): find the parent GetPage. If it has no children, add a children: [ ... ] list. Put the new GetPage inside that list. Leave the parent view and controller untouched.

If _Paths does not exist, use Routes.{routeId} as the name: and set Routes.{routeId} = '/{route-segment}'.

Done

The work is done when:

  • The three dart files exist at the destination and compile against the templates above.
  • app_routes.dart declares the new path.
  • app_pages.dart imports the view and binding and lists the GetPage (top-level or as a child).

Examples

get create screen:home / "create a home screen"

lib/app/modules/home/bindings/home_binding.dart
lib/app/modules/home/controllers/home_controller.dart
lib/app/modules/home/views/home_view.dart

Routes.home = _Paths.home, _Paths.home = '/home', plus a top-level GetPage.

get create screen:login on home / "create a login screen on home"

lib/app/modules/home/login/bindings/login_binding.dart
lib/app/modules/home/login/controllers/login_controller.dart
lib/app/modules/home/login/views/login_view.dart

Routes.login = _Paths.home + _Paths.login, _Paths.login = '/login', and a child GetPage on home.

Frequently asked questions

What does the Create Screen AI skill do?

Creates a GetX screen module (controller, view, binding) under lib/app/modules and registers it in app routes. Use whenever the user asks to create a screen, page, or module, says get create screen, get create page, get create module, or wants a new GetX view plus controller plus binding with routing.

Why use Create Screen on TypingMind?

Because you install it once and use it with any model. Create Screen is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Create Screen in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/EmadBeltaje/flutter_getx_template/tree/master/.agent/skills/create-screen. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Create Screen?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Create Screen?

As many as you like. As long as a model supports skills, you can use Create Screen with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Create Screen AI skill free?

Yes. It is published on GitHub by EmadBeltaje under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇