| #!/bin/bash | |
| source /venv/main/bin/activate | |
| COMFYUI_DIR=${WORKSPACE}/ComfyUI | |
| # Packages are installed after nodes so we can fix them... | |
| APT_PACKAGES=( | |
| #"package-1" | |
| #"package-2" |
| --- | |
| description: Code index maps all types, methods and properties across the project files. Mirrors folder structure to give instant high-level view of codebase architecture - perfect for grasping project scope and organization at a glance. | |
| globs: **/*.{swift,md} | |
| --- | |
| Format: | |
| ./Directory/ | |
| struct TypeName: Protocols | |
| - property: Type | |
| - method(param: Type) -> ReturnType |
You are an expert software architect and technical project planner. Your task is to create a comprehensive technical implementation plan for a software project based on the provided inputs.
do you know googly python-fire? Python Fire is a library for automatically generating command line interfaces (CLIs) from absolutely any Python object. I want a similar library, but instead of a CLI it generates amazing web apps for any python project!
You are an expert software architect and technical project planner. Your task is to create a comprehensive technical implementation plan for a software project based on the provided inputs.
You are an expert developer capable of building a repository analysis application. Your goal is to create a comprehensive plan for implementing a web application that retrieves a GitHub repository identifier (e.g., 127.0.0.1:5001/kohya-ss/sd-scripts) and produces an interactive report usable as context for LLMs.
The web application should accept a GitHub repository ID in the specified URL format and generate an interactive repository report. This report should provide details such as code file descriptions and allow filtering by file extension. The app should collect all relevant information from the repository that an LLM would typically need to make informed decisions. It is up to you to decide what type of information to include, while also offering users the
How to use a .xcconfig file and a .plist with a Swift Package Manager based project.
| /*: | |
| This is a concept re-implementation of the @Binding and @State property wrappers from SwiftUI | |
| The only purpose of this code is to implement those wrappers myself | |
| just to understand how they work internally and why they are needed, | |
| ⚠️ This is not supposed to be a reference implementation nor cover all | |
| subtleties of the real Binding and State types. | |
| The only purpose of this playground is to show how re-implementing | |
| them myself has helped me understand the whole thing better |
| #!/usr/bin/env python3 | |
| import requests | |
| import json | |
| import sys | |
| # Constants | |
| CURRENT_VERSION = "1.1.0" | |
| OPENROUTER_URL = "https://openrouter.ai/api/v1/chat/completions" |
| import base64 | |
| import csv | |
| import io | |
| import os | |
| import time | |
| from datetime import datetime, timedelta | |
| from typing import Tuple | |
| import numpy as np | |
| import pyautogui |
| async def run_async(func, *args, **kwargs) -> T: | |
| """ | |
| Runs a synchronous function in an asynchronous manner. | |
| """ | |
| async def wrapper() -> T: | |
| try: | |
| return await loop.run_in_executor( | |
| None, functools.partial(func, *args, **kwargs) | |
| ) |