Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Write a Blog Post: Using the Screen Toolkit with Goose 🦢 #24

Open
4 tasks
Tracked by #32
blackgirlbytes opened this issue Oct 29, 2024 · 7 comments
Open
4 tasks
Tracked by #32

Write a Blog Post: Using the Screen Toolkit with Goose 🦢 #24

blackgirlbytes opened this issue Oct 29, 2024 · 7 comments

Comments

@blackgirlbytes
Copy link
Collaborator

blackgirlbytes commented Oct 29, 2024

Write a Blog Post: Using the Screen Toolkit with Goose 🦢

Goose is your on-machine developer agent, automating engineering tasks seamlessly within your IDE or terminal. Guided by you, it can intelligently assess your project's needs, generate code modifications, and implement changes on its own.
Learn more about Goose in our documentation.

Once your content is merged, it will be featured on our Community Content site!

Example content

regularmarkdowneditor.1.mp4
upgrade-u-supercharging-intellij-with-an-open-source-ai-agentmp4-156132.mp4

🚀 Goal

Write a blog post sharing your experience using the Screen Toolkit in Goose. Help others understand how this toolkit can be used for debugging, design work, and other creative applications by giving Goose the ability to see and analyze your screen.

🤝 How You Can Contribute

Write about things like:

  • Setting up the Screen Toolkit
  • Using screenshots for debugging
  • Design assistance workflows
  • UI/UX improvements with Goose
  • Creative applications you've discovered
  • Tips and best practices
  • Integration with other toolkits

🔑 Tasks and Acceptance Criteria

  • Write a blog post about using the Screen Toolkit
  • Host your blog post on your preferred platform (dev.to, Medium, personal blog, etc.)
  • Add your content to the content/content.json file
  • Create a pull request with your changes

Your contribution in content.json must include:

{
    "type": "blog",
    "thumbnail": "./img/your-thumbnail.png",
    "title": "Your Blog Post Title",
    "link": "https://linktoyourblog.com",
    "contributor": "Your Name"
}

🌟 Resources

Full episodes on Goose to understand more

How to Build an AI-Powered GitHub Action

Upgrade U: Supercharging IntelliJ with an Open Source AI Agent

Getting Started

  1. Comment ".take" on this issue to get assigned
  2. Fork the repository and create a new branch
  3. Write your blog post
  4. Submit a PR with your content.json addition
  5. Wait for review and address any feedback

Questions?

If you have any questions or need clarification, please comment on this issue!
Happy writing! 🦢

@CBID2
Copy link

CBID2 commented Nov 1, 2024

.take

Copy link

github-actions bot commented Nov 1, 2024

Thanks for taking this issue! Let us know if you have any questions! Join our Discord https://discord.gg/DCAZKnGZFa

@blackgirlbytes
Copy link
Collaborator Author

@CBID2 nice to see you here ! if you need help with Goose or the screen toolkit. Let me know!

@blackgirlbytes
Copy link
Collaborator Author

@CBID2 Hi Chrissy!! How's the progress on this going? I actually wrote a blog post on this exact topic. I hope it helps you out https://dev.to/blackgirlbytes/how-my-ai-dev-agent-turns-screenshots-into-ui-updates-189p

@CBID2
Copy link

CBID2 commented Nov 13, 2024

@CBID2 Hi Chrissy!! How's the progress on this going? I actually wrote a blog post on this exact topic. I hope it helps you out https://dev.to/blackgirlbytes/how-my-ai-dev-agent-turns-screenshots-into-ui-updates-189p

Hey @blackgirlbytes. I've been so busy with family stuff lately so I didn't get a chance to start yet. Once I'm back, I'll get right to it

@blackgirlbytes
Copy link
Collaborator Author

okidoke @CBID2 understood! hope everything gets better

@blackgirlbytes
Copy link
Collaborator Author

Kind reminder that Loose Goose November ends November 20 at 11:59 pm ET, so if you wanted to be eligible for prizes, you only have a few hours left, but if you just want to work on this for fun after the deadline then let me know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants